From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: [StGit PATCH] It doesn't make sense to sink below an unapplied patch
Date: Sun, 16 Sep 2007 23:20:36 +0200 [thread overview]
Message-ID: <87veaab93v.fsf@morpheus.local> (raw)
In-Reply-To: 20070915232252.GA25507@diana.vm.bytemark.co.uk
Karl Hasselström <kha@treskal.com> writes:
> Another idea that's been kicked around is to have a general reorder
> command, that spawns an editor and lets you move around (and delete)
> patch names until you're satisfied. (This too would be implemented in
> terms of push and pop of single patches.)
This of course sounds very much like "git rebase -i", but the
semantics would maybe not be identical.
One feature from rebase I'd like to see if this was implemented is the
"squash" option to join two patches. But it would probably be called
"fold" to keep with stgit terminology.
Another way of doing this editing is to do it interactively,
interacting with the patches directly using a UI, such as an Emacs
editing mode, or a custom text or graphical UI. As you might guess,
I've been thinking a little of an Emacs interface, but nothing has
been written yet.
--
David Kågedal
next prev parent reply other threads:[~2007-09-16 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070914002031.GC23330@diana.vm.bytemark.co.uk>
[not found] ` <20070914005231.17533.17120.stgit@yoghurt>
[not found] ` <9e4733910709131822s3c519a3bj7e42c0ecaa89fb6e@mail.gmail.com>
[not found] ` <20070914060456.GA27014@diana.vm.bytemark.co.uk>
[not found] ` <9e4733910709140715g3cc3e47fu2eb24eed6d4e2c08@mail.gmail.com>
[not found] ` <20070914150609.GA319@diana.vm.bytemark.co.uk>
[not found] ` <9e4733910709140918wbe94b5eu6ec326b25b0f3d42@mail.gmail.com>
2007-09-15 23:22 ` [StGit PATCH] It doesn't make sense to sink below an unapplied patch Karl Hasselström
2007-09-16 21:20 ` David Kågedal [this message]
2007-09-17 9:49 ` Karl Hasselström
2007-09-16 21:41 ` Jon Smirl
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=87veaab93v.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--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).