From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 3/3] diffstat generation in hooks--update was passing "^baserev" to git-diff-tree
Date: Tue, 13 Feb 2007 18:34:34 +0000 [thread overview]
Message-ID: <200702131834.36001.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702130856580.8424@woody.linux-foundation.org>
On Tuesday 2007, February 13, Linus Torvalds wrote:
> This is wrong.
>
> newrev ^baserev
>
> is right. The "not baserev" tells diff-tree that the baserev is the
Right. It's all come back to me now you've explained it; I obviously
understood it when I wrote it, but it leaked out in the interim :-). I
was surprised because I've been using the hook for ages and the output
seemed right. :-)
Junio - please ignore this patch.
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
prev parent reply other threads:[~2007-02-13 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 14:24 [PATCH 3/3] diffstat generation in hooks--update was passing "^baserev" to git-diff-tree Andy Parkins
2007-02-13 15:37 ` Johannes Sixt
2007-02-13 16:32 ` Andy Parkins
2007-02-13 17:16 ` Johannes Sixt
2007-02-13 17:03 ` Linus Torvalds
2007-02-13 18:34 ` Andy Parkins [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=200702131834.36001.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).