From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: qgit idea: interface for cherry-picking
Date: Sun, 02 Jul 2006 23:46:20 +0200 [thread overview]
Message-ID: <e89eqj$npu$1@sea.gmane.org> (raw)
In-Reply-To: e5bfff550607021433l1987c32apf4453b52fc2f3e63@mail.gmail.com
Marco Costalba wrote:
> On 7/2/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> Currently in qgit one can git-format-patch a commit. It woul be nice
>> if one would be able to git-cherry-pick and git-cherry-pick -n a commit
>> (denoting the head, i.e. where cherry pick would be applied to). It would
>> be very usefull in reordering patches (cleaning up history).
>
> Currently in qgit you can git-format-patch a commit series and git-am
> a given patch file series.
> This can be done transparently with a drag & drop mechanic:
>
> 1) Open the source repository
> 2) Then open a new qgit instance (File->Open in a new window...)
> 3) Open the destination repository in the new qgit window
> 4) Drag & drop selected commits (multi selection in supported) from
> source to destination.
Does multi selection commits all selected commits as one merged commit?
> I normally use this instead of git-cherry-pick that, I admit, I don't
> know very well, so please I need some more hints on how to upgrade
> this behaviour introducing git.cherry-pick support.
I use git-cherry-pick -n to join few patches into one, or with editing the
result to split one patch/commit into few smaller.
git-cherry-pick [-n] <commit> picks up a commit and drops it on top of
current branch. I'd like to see it in context menu for current commit,
i.e. "cherry-pick to <head>", where <head> will be replaced by current
branch name, or/and "cherry-pick -n to <head>".
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-02 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 19:01 qgit idea: interface for cherry-picking Jakub Narebski
2006-07-02 21:33 ` Marco Costalba
2006-07-02 21:46 ` Jakub Narebski [this message]
2006-07-02 22:04 ` Marco Costalba
2006-07-02 22:54 ` Jakub Narebski
2006-07-03 5:45 ` Marco Costalba
2006-07-03 6:42 ` Junio C Hamano
2006-07-03 11:18 ` Marco Costalba
2006-07-03 20:03 ` Junio C Hamano
2006-07-04 6:22 ` Marco Costalba
2006-07-04 6:39 ` Jakub Narebski
2006-07-04 11:58 ` Marco Costalba
2006-07-04 13:29 ` Jakub Narebski
2006-07-04 18:38 ` Marco Costalba
2006-07-04 6:41 ` Junio C Hamano
2006-07-04 7:02 ` Jakub Narebski
2006-07-04 11:21 ` Marco Costalba
2006-07-04 18:23 ` Marco Costalba
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='e89eqj$npu$1@sea.gmane.org' \
--to=jnareb@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 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).