From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Chris Packham <judge.packham@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] rebase--interactive: Add "sign" command
Date: Wed, 3 Aug 2016 18:15:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1608031813410.107993@virtualbox> (raw)
In-Reply-To: <xmqqr3a5al7z.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Wed, 3 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > ... my Git garden shears [*1*] (essentially, what
> > git rebase --interactive --preserve-merges *should* have been).
>
> Any plan to fold it into "git rebase -i" as a new (improved) mode of
> operation, by the way?
It was my plan to integrate it into the sequencer, once the rebase--helper
landed in `master`. Little did I know how long it would take to get this
done...
My loose idea was to deprecate --preserve-merges after introducing a
--recreate-branches, or some such. But enough of that. The rebase--helper
needs to get here first.
> > However, I could imagine that we actually want this to be more extensible.
> > After all, all you are doing is to introduce a new rebase -i command that
> > does nothing else than shelling out to a command.
>
> Yup, I tend to agree.
Awesome!
Ciao,
Dscho
next prev parent reply other threads:[~2016-08-03 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 8:47 [RFC/PATCH] rebase--interactive: Add "sign" command Chris Packham
2016-08-03 14:31 ` Johannes Schindelin
2016-08-03 15:19 ` Johannes Schindelin
2016-08-03 16:08 ` Junio C Hamano
2016-08-03 16:15 ` Johannes Schindelin [this message]
2016-08-03 18:08 ` Jeff King
2016-08-04 0:53 ` Chris Packham
2016-08-04 16:05 ` Junio C Hamano
2016-08-05 16:04 ` Johannes Schindelin
2016-08-04 0:41 ` Chris Packham
2016-08-03 15:58 ` Junio C Hamano
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=alpine.DEB.2.20.1608031813410.107993@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=judge.packham@gmail.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;
as well as URLs for NNTP newsgroup(s).