From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-cherries
Date: Fri, 02 Mar 2012 12:19:42 +0100 [thread overview]
Message-ID: <87ehtb8d2p.fsf@gnuvola.org> (raw)
In-Reply-To: 20120227192746.GC1600@sigill.intra.peff.net
() Jeff King <peff@peff.net>
() Mon, 27 Feb 2012 14:27:46 -0500
So if I understand correctly, this just creates a series of commits, one
per hunk, of what's in your working tree. And the commit messages won't
be useful, so this is really about recording the work somewhere so that
you can pick it out later using "git cherry-pick --no-commit", make a
real commit from some subset of the cherries, and then throw away the
cherries?
I think you could do this more simply by putting everything in a single
throw-away commit, then using "git checkout -p $throwaway" to pick the
individual cherries from the single commit. You don't grab the commit
message from $throwaway as you might with cherry-pick, but by definition
it's not a very good commit message anyway.
Cool; "git checkout -p" was what i was missing. Thanks for the tip!
prev parent reply other threads:[~2012-03-02 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 10:56 git-cherries Thien-Thi Nguyen
2012-02-27 19:27 ` git-cherries Jeff King
2012-03-02 11:19 ` Thien-Thi Nguyen [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=87ehtb8d2p.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).