git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Catalin Marinas" <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: [StGit PATCH] It doesn't make sense to sink below an unapplied patch
Date: Sun, 16 Sep 2007 17:41:27 -0400	[thread overview]
Message-ID: <9e4733910709161441j43e69ee2j6c57489c4b0eafbb@mail.gmail.com> (raw)
In-Reply-To: <20070915232252.GA25507@diana.vm.bytemark.co.uk>

On 9/15/07, Karl Hasselström <kha@treskal.com> wrote:
> On 2007-09-14 12:18:17 -0400, Jon Smirl wrote:
> > 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

      parent reply	other threads:[~2007-09-16 21:41 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
2007-09-17  9:49                 ` Karl Hasselström
2007-09-16 21:41               ` Jon Smirl [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=9e4733910709161441j43e69ee2j6c57489c4b0eafbb@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.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).