From: Chris Friesen <chris.friesen@genband.com>
To: git@vger.kernel.org
Subject: [feature request] embed original commit info in cherry-pick
Date: Thu, 24 Feb 2011 12:30:33 -0600 [thread overview]
Message-ID: <4D66A3C9.7050001@genband.com> (raw)
If I cherry-pick a bugfix from a more recent version of a project, it
would be useful to have an indication somewhere in the commit
information of where it originally came from.
That way, if I then upgrade to a newer version of the software it
becomes obvious that I don't need to worry about porting that commit
forwards because it's already been handled upstream.
As it stands, it's not immediately obvious what was cherry-picked vs
what was developed locally.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next reply other threads:[~2011-02-24 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 18:30 Chris Friesen [this message]
2011-02-24 19:12 ` [feature request] embed original commit info in cherry-pick Jeff King
2011-02-24 19:17 ` Chris Friesen
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=4D66A3C9.7050001@genband.com \
--to=chris.friesen@genband.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 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).