git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: ab/send-email-transferencoding-fix, was Re: What's cooking in git.git (May 2019, #04; Tue, 28)

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 29, 2019, 12:36 UTC
Message-ID
<877ea9mo98.fsf@evledraar.gmail.com>
In-Reply-To
<nycvar.QRO.7.76.6.1905291424140.44@tvgsbejvaqbjf.bet>
On Wed, May 29 2019, Johannes Schindelin wrote:
Show 29 quoted lines
> 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.

Previous: Johannes SchindelinNext: Junio C Hamano
Message 8 of 11 in “What's cooking in git.git (May 2019, #04; Tue, 28)”
  1. Junio C HamanoMay 28, 2019
  2. Jeff KingMay 28, 2019
  3. Junio C HamanoMay 29, 2019
  4. Jeff KingMay 30, 2019
  5. Johannes SchindelinMay 30, 2019
  6. Derrick StoleeMay 30, 2019
  7. ab/send-email-transferencoding-fix, was Re: What's cooking in git.git (May 2019, #04; Tue, 28)Johannes Schindelin, May 29, 2019
  8. Ævar Arnfjörð BjarmasonMay 29, 2019
  9. Junio C HamanoMay 29, 2019
  10. Johannes SchindelinMay 29, 2019
  11. Junio C HamanoMay 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.