Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

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

From: Jon Smirl <hidden>
Date: 2016-06-15 22:43:35

On 9/15/07, Karl Hasselström [off-list ref] wrote:
On 2007-09-14 12:18:17 -0400, Jon Smirl wrote:
quoted
Another way to handle this would be to eliminate the ability of
pop/push to reorder and extend sink/float to handle unapplied
patches.
I think that I'd like the latter without the former -- that is,
teaching sink/float how to handle unapplied patches, and leaving
push/pop as is. That'll let you do what you tried to do in the first
place, and will leave us with a more redundant command set, but I
don't think that's bad.
The stack model may be too simplistic. My current patches involve four
groups, there is ordering in the group but the groups can be applied
independently. Patches could be marked as depending on another
patch/group. You could then mark patches applied/unapplied and stg
would sort out the order. Allowing group names would make this easier.

The mm kernel has 1,500 patches. It must be a pain trying to keep
these in a linear order.

The git diff output format could be extended with
Depends-on/Group-name lines. That would let Andrew import the
dependencies.

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.)

--
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

-- 
Jon Smirl
jonsmirl@gmail.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help