From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Updated version, was Re: RFC: Patch editing
Date: Thu, 01 Mar 2007 15:59:21 -0800 [thread overview]
Message-ID: <7vwt20o6qu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0703020020470.22628@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Fri, 2 Mar 2007 00:30:03 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> My plans are _not_ to turn this into git-rebase--interactive.sh, as I
> originally planned. Instead, I will try to make git-rebase a builtin, and
> add a "-i" flag which does the equivalent of this script.
>
> BTW would people be mad at me if I did _not_ imitate git-rebase.sh (call
> format-patch and feed that into apply), but rather used cherry-pick
> throughout?
Then that C built-in would not replace git-rebase but only
"git-rebase -m".
I very often find it easier to deal with a conflicting rebase by
editing the patch text, so yes I would imagine I would be rather
upset, but I do not know about others.
prev parent reply other threads:[~2007-03-02 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 21:59 RFC: Patch editing Johannes Schindelin
2007-02-26 13:18 ` Peter Baumann
2007-02-26 18:03 ` Shawn O. Pearce
2007-02-26 18:52 ` Johannes Schindelin
2007-02-26 18:56 ` Shawn O. Pearce
2007-02-26 19:51 ` Junio C Hamano
2007-02-27 7:14 ` Daniel Barkalow
2007-02-27 11:54 ` Johannes Schindelin
2007-02-27 17:35 ` Daniel Barkalow
2007-02-27 20:07 ` Johannes Schindelin
2007-02-27 22:07 ` Daniel Barkalow
2007-02-27 22:37 ` Johannes Schindelin
2007-02-28 10:13 ` Karl Hasselström
2007-03-01 23:30 ` Updated version, was " Johannes Schindelin
2007-03-01 23:59 ` Junio C Hamano [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=7vwt20o6qu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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).