From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: ab/send-email-transferencoding-fix, was Re: What's cooking in git.git (May 2019, #04; Tue, 28)
Date: Wed, 29 May 2019 14:36:03 +0200 [thread overview]
Message-ID: <877ea9mo98.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1905291424140.44@tvgsbejvaqbjf.bet>
On Wed, May 29 2019, Johannes Schindelin wrote:
> Hi Junio & Ævar,
>
> On Tue, 28 May 2019, Junio C Hamano wrote:
>
>> * ab/send-email-transferencoding-fix (2019-05-19) 7 commits
>> - send-email: fix regression in sendemail.identity parsing
>> - send-email: document --no-[to|cc|bcc]
>> - send-email: fix broken transferEncoding tests
>> - send-email: remove cargo-culted multi-patch pattern in tests
>> (merged to 'next' on 2019-05-13 at 38c6a1e7e0)
>> + send-email: do defaults -> config -> getopt in that order
>> + send-email: rename the @bcclist variable for consistency
>> + send-email: move the read_config() function above getopts
>>
>> Since "git send-email" learned to take 'auto' as the value for the
>> transfer-encoding, it by mistake stopped honoring the values given
>> to the configuration variables sendemail.transferencoding and/or
>> sendemail.<ident>.transferencoding. This has been corrected to
>> (finally) redoing the order of setting the default, reading the
>> configuration and command line options.
>>
>> Will merge to 'next'.
>
> I just sent a reminder that the tip commit is broken under NO_PERL, and
> accompanied the report with a diff that could be squashed in. Ævar, please
> have a look and say yay or nay, and please let's only let this enter
> `next` once it is fixed (because otherwise the Azure Pipeline will spam me
> every tim `next` is psuhed -- thanks, Emily, now I mistype this every
> single time).
Sorry about missing this. Your prereq addition in
<nycvar.QRO.7.76.6.1905291106540.44@tvgsbejvaqbjf.bet> looks obviously
correct to me.
next prev parent reply other threads:[~2019-05-29 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 22:08 What's cooking in git.git (May 2019, #04; Tue, 28) Junio C Hamano
2019-05-28 22:26 ` Jeff King
2019-05-29 16:53 ` Junio C Hamano
2019-05-30 11:51 ` Jeff King
2019-05-30 15:01 ` Johannes Schindelin
2019-05-30 18:29 ` Derrick Stolee
2019-05-29 12:26 ` ab/send-email-transferencoding-fix, was " Johannes Schindelin
2019-05-29 12:36 ` Ævar Arnfjörð Bjarmason [this message]
2019-05-29 17:31 ` Junio C Hamano
2019-05-29 18:10 ` Johannes Schindelin
2019-05-29 19:54 ` Junio C Hamano
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=877ea9mo98.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.