From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2019, #02; Tue, 14)
Date: Mon, 13 May 2019 15:20:51 -0700 [thread overview]
Message-ID: <CABPp-BGPrDfHjQoASFFbyt2v3Aa6vie5H5U2KOWUnu=_NEiPyA@mail.gmail.com> (raw)
In-Reply-To: <xmqqa7fqbahj.fsf@gitster-ct.c.googlers.com>
On Mon, May 13, 2019 at 12:27 PM Junio C Hamano <gitster@pobox.com> wrote:
> * en/fast-export-encoding (2019-05-13) 5 commits
> - fast-export: do automatic reencoding of commit messages only if requested
> - fast-export: differentiate between explicitly utf-8 and implicitly utf-8
> - fast-export: avoid stripping encoding header if we cannot reencode
> - fast-import: support 'encoding' commit header
> - t9350: fix encoding test to actually test reencoding
>
> The "git fast-export/import" pair has been taught to handle commits
> with log messages in encoding other than UTF-8 better.
>
> Will merge to 'next'.
> cf. <20190510205335.19968-1-newren@gmail.com>
I sent out a v4 this morning with Torsten's suggested YES|NO wording,
your suggestion of more aliases for "yes"/"no", and based on Dscho's
clarification I was able to update the tests to be more precise. I
again tested with Dscho's gitgitgadget Azure pipelines integration to
verify it works on the major platforms. Could you merge it (cf.
<20190513164722.31534-1-newren@gmail.com>) instead of the v3 you
currently have in en/fast-export-encoding?
Elijah
next prev parent reply other threads:[~2019-05-13 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 16:11 What's cooking in git.git (May 2019, #02; Tue, 14) Junio C Hamano
2019-05-13 22:20 ` Elijah Newren [this message]
2019-05-14 9:54 ` js/difftool-no-index, was " Johannes Schindelin
2019-05-15 1:28 ` Junio C Hamano
2019-05-15 8:24 ` Johannes Schindelin
2019-05-15 8:50 ` Junio C Hamano
2019-05-17 18:27 ` Johannes Schindelin
2019-05-19 1:44 ` Junio C Hamano
2019-05-21 22:28 ` Johannes Schindelin
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='CABPp-BGPrDfHjQoASFFbyt2v3Aa6vie5H5U2KOWUnu=_NEiPyA@mail.gmail.com' \
--to=newren@gmail.com \
--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.
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).