git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [StGit PATCH] It doesn't make sense to sink below an unapplied patch

From
David Kågedal <davidk@lysator.liu.se>
Date
Sep 16, 2007, 21:20 UTC
Message-ID
<87veaab93v.fsf@morpheus.local>
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
Previous: Karl HasselströmNext: Karl Hasselström
Message 2 of 4 in “Re: [StGit PATCH] It doesn't make sense to sink below an unapplied patch”
  1. Karl HasselströmSep 15, 2007
  2. David KågedalSep 16, 2007
  3. Karl HasselströmSep 17, 2007
  4. Jon SmirlSep 16, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.