From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2018, #03; Wed, 15)
Date: Thu, 16 Aug 2018 07:58:01 -0700 [thread overview]
Message-ID: <xmqqlg96gxza.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kar1UwZEX9d=+e57ZJCy7YaqKSPExOexp8_t=G1VjwY2g@mail.gmail.com> (Stefan Beller's message of "Wed, 15 Aug 2018 19:35:23 -0700")
Stefan Beller <sbeller@google.com> writes:
>>
>> * sb/config-write-fix (2018-08-08) 3 commits
>> - git-config: document accidental multi-line setting in deprecated syntax
>> - config: fix case sensitive subsection names on writing
>> - t1300: document current behavior of setting options
>>
>> Recent update to "git config" broke updating variable in a
>> subsection, which has been corrected.
>>
>> Expecting a reroll.
>> cf. <CAGZ79kZ1R8sxmtfgPOQcpoWM7GWV1qiRaqMq_zhGyKBB3ARLjg@mail.gmail.com>
>
> That reroll happened and you picked it up,
> cf. https://public-inbox.org/git/20180808195020.37374-1-sbeller@google.com/
Thanks for a quick update. I do not think I saw any other issues
raised and a quick rescan of the patches does not raise any flags,
so perhaps we should mark it to be merged to 'next' soonish.
next prev parent reply other threads:[~2018-08-16 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 23:01 What's cooking in git.git (Aug 2018, #03; Wed, 15) Junio C Hamano
2018-08-16 2:35 ` Stefan Beller
2018-08-16 14:58 ` Junio C Hamano [this message]
2018-08-16 13:15 ` Derrick Stolee
2018-08-16 14:43 ` Stefan Beller
2018-08-17 14:56 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlg96gxza.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).