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 (Oct 2018, #05; Fri, 26)
Date: Sat, 27 Oct 2018 16:29:56 +0900 [thread overview]
Message-ID: <xmqqwoq3alu3.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kbjKZSHfHbDykkob1w21RTB9tgCCYVrOD=0C8aAFGncTQ@mail.gmail.com> (Stefan Beller's message of "Fri, 26 Oct 2018 12:04:55 -0700")
Stefan Beller <sbeller@google.com> writes:
>>
>> * sb/strbuf-h-update (2018-09-29) 1 commit
>> (merged to 'next' on 2018-10-26 at e4ad935cb0)
>> + strbuf.h: format according to coding guidelines
>>
>> Code clean-up to serve as a BCP example.
>>
>> Will merge to 'master'.
>> Further clean-up patches may need to follow soon before this
>> change escapes to 'master'.
>
> We have a contradicting statement here, which can be either an
> issue or an oversight.
"may need to" takes a volunteer to do so; it does not have to take
the patch hostage to the lack of such a volunteer.
next prev parent reply other threads:[~2018-10-27 7:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:57 What's cooking in git.git (Oct 2018, #05; Fri, 26) Junio C Hamano
2018-10-26 12:09 ` js/mingw-http-ssl, was " Johannes Schindelin
2018-10-26 13:19 ` Junio C Hamano
2018-10-29 13:22 ` Johannes Schindelin
2018-10-30 2:09 ` Junio C Hamano
2018-10-30 2:22 ` Eric Sunshine
2018-10-30 5:37 ` Junio C Hamano
2018-10-30 5:49 ` Kaartic Sivaraam
2018-10-30 10:16 ` Johannes Schindelin
2018-10-26 19:04 ` Stefan Beller
2018-10-27 7:29 ` Junio C Hamano [this message]
2018-10-27 3:45 ` Taylor Blau
2018-10-27 6:27 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwoq3alu3.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.
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 NNTP newsgroup(s).