From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Tweak git-diff-tree -v output further (take 2).
Date: Fri, 06 May 2005 14:47:32 -0700 [thread overview]
Message-ID: <427BE5F4.3040602@zytor.com> (raw)
In-Reply-To: <7vbr7ocfj7.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> (This one is simpler than the previous one I just sent out)
>
> The first hunk of this is a pure bugfix---it guards us against a
> commit message that does not end with a newline.
No it doesn't. What it does is "guard" you against a commit message
which contains a null character. What's not entirely clear is if that's
what you wanted to do.
-hpa
prev parent reply other threads:[~2005-05-06 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 19:37 [PATCH] Tweak git-diff-tree -v output further (take 2) Junio C Hamano
2005-05-06 21:40 ` Linus Torvalds
2005-05-06 22:05 ` Junio C Hamano
2005-05-06 21:47 ` H. Peter Anvin [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=427BE5F4.3040602@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/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