From: Alex Riesen <raa.lkml@gmail.com>
To: luuk@pobox.com
Cc: git@vger.kernel.org
Subject: Re: Difficulty with getting an accurate changelog after cherry-picking and merging.
Date: Tue, 22 Jul 2008 23:09:24 +0200 [thread overview]
Message-ID: <20080722210924.GE5113@blimp.local> (raw)
In-Reply-To: <7dc909980807221338g707d6104ob8b1534cdf02a77a@mail.gmail.com>
Luuk Paulussen, Tue, Jul 22, 2008 22:38:19 +0200:
> 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.
Cherry-picked commits are completely new commits and have no relation
to the original commits whatsoever. Of course, they will be shown.
It is literally a change made again, as if you typed it all in and
committed.
next prev parent reply other threads:[~2008-07-22 21:10 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 [this message]
2008-07-22 21:14 ` Johannes Schindelin
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=20080722210924.GE5113@blimp.local \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=luuk@pobox.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