From: Christian Himpel <chressie@googlemail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Christian Himpel <chressie@googlemail.com>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [PATCH] git-am: force egrep to use correct characters set
Date: Mon, 28 Sep 2009 14:09:49 +0200 [thread overview]
Message-ID: <20090928120949.GA3964@mrslave> (raw)
In-Reply-To: <4AC0877E.7020204@viscovery.net>
On Mon, Sep 28, 2009 at 11:53:02AM +0200, Johannes Sixt wrote:
> Christian Himpel schrieb:
> >> The case identified by Christian is certainly important because it is
> >> applied to a file whose contents can be anything, and the purpose of the
> >> check is to identify the text as an mbox file, whose header section can be
> >> only US-ASCII by definition. So, I think it has merit to apply the patch.
> >
> > Yes. It seems that this is the only place where it is important to match
> > just the ASCII printable characters.
>
> There is another place in git-am.sh where a sed expression with a range
> looks at the input file, doesn't it? Isn't it critical, too?
>
> if test -f "$dotest/rebasing" &&
> commit=$(sed -e 's/^From \([0-9a-f]*\) .*/\1/' \
> -e q "$dotest/$msgnum") &&
> test "$(git cat-file -t "$commit")" = commit
> then ...
It seems to be the line generated from 'git format-patch' that is tested
here. It specifies the SHA1 of the commit that is converted into a mbox
patch by 'format-patch'. Hence, I don't see it critical here (until
someone edits this line by hand).
Regards,
chressie
prev parent reply other threads:[~2009-09-28 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 15:14 [PATCH 1/2] git-am: fixed patch_format detection according to RFC2822 Christian Himpel
2009-09-25 15:17 ` [PATCH 2/2] git-am: force egrep to use correct characters set Christian Himpel
2009-09-25 15:45 ` [PATCH 2/2 v2] " Christian Himpel
2009-09-25 16:43 ` [PATCH] " Christian Himpel
2009-09-27 7:40 ` Jeff King
2009-09-28 6:55 ` Christian Himpel
2009-09-28 7:16 ` Jeff King
2009-09-28 8:12 ` Johannes Sixt
2009-09-28 9:32 ` Christian Himpel
2009-09-28 9:53 ` Johannes Sixt
2009-09-28 12:09 ` Christian Himpel [this message]
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=20090928120949.GA3964@mrslave \
--to=chressie@googlemail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peff@peff.net \
/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.