From: Johannes Sixt <J.Sixt@eudaptics.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] diffstat generation in hooks--update was passing "^baserev" to git-diff-tree
Date: Tue, 13 Feb 2007 18:16:26 +0100 [thread overview]
Message-ID: <45D1F26A.28FEADD8@eudaptics.com> (raw)
In-Reply-To: 200702131632.37401.andyparkins@gmail.com
Andy Parkins wrote:
> > You still need to derive a merge-base, but only to detect the forced
> > update and to format the message. Then you should use --not $baserev
> > instead of ^$baserev just in case there is more than one merge-base.
>
> Are you suggesting something like this?
>
> git-rev-parse --not --all $baserev | git-rev-list --stdin --pretty $newrev
>
> Which would start showing from $newrev but would exclude all baserevs and all
> existing branches.
You are using ^$baserev in two instances.
(1) in a for loop which obviously is intended as a table of contents
(revs plus rev-type (can this be anything else than 'commit'?)). Here
you should use
git-rev-list $newrev --not $baserev
(2) later to print the log messages for all new revs. Here you use just
this:
git-rev-list --pretty $oldrev..$newrev
Then the diffstat:
git-diff-tree --no-color --stat -M -C --find-copies-harder \
$oldrev $newrev
This reflects the modifications of the revisions that have just been
listed *only* in the fast-forward case. But even in the forced update
case it tells how the old tree transformed into the new tree, and for
this reason nothing more complicated is needed, IMO.
-- Hannes
next prev parent reply other threads:[~2007-02-13 17:14 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 [this message]
2007-02-13 17:03 ` Linus Torvalds
2007-02-13 18:34 ` Andy Parkins
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=45D1F26A.28FEADD8@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.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 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.