From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Luuk Paulussen <luuk.paulussen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Difficulty with getting an accurate changelog after cherry-picking and merging.
Date: Tue, 22 Jul 2008 22:14:42 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807222209180.8986@racer> (raw)
In-Reply-To: <7dc909980807221338g707d6104ob8b1534cdf02a77a@mail.gmail.com>
Hi,
On Wed, 23 Jul 2008, Luuk Paulussen wrote:
> I'm trying to generate an accurate changelog of changes between 2 tags
> on a branch. There is a merge between these 2 points which includes
> changes that were cherry-picked before the start point. This causes the
> changelog to show these changes, despite them already existing before
> the start point of the log.
>
> [...]
>
> I have tried git-cherry and git-log with --cherry-pick and various
> things with git-rev-list and git-merge-base.
cherry and --cherry-pick will only skip patches that are on the
uninteresting side of a "..." range.
I guess that
$ git log --cherry-pick master...HEAD^
should filter the commits out, but I haven't tried.
> git cherry-pick :/test1
Heh, that is the first time I see :/ in the wild. I do not use it
anymore, and in your case, I would have written "git cherry-pick master^4"
to be more precise (and not accidentally pick up a wrong one).
Ciao,
Dscho
prev parent reply other threads:[~2008-07-22 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 20:38 Difficulty with getting an accurate changelog after cherry-picking and merging Luuk Paulussen
2008-07-22 21:09 ` Alex Riesen
2008-07-22 21:14 ` Johannes Schindelin [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=alpine.DEB.1.00.0807222209180.8986@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=luuk.paulussen@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox