Re: [Quilt-dev] [PATCH] quilt drop command

[Greg KH]

On Thu, Jun 02, 2005 at 05:13:41PM -0500, Josh Boyer wrote:
> > > This could be highly useful to people using a single tree for multiple
> > > patch sets that don't really have anything to do with each other.  For
> > > example, maintaining two separate driver trees.
> > 
> > I think some people do that already (Greg KH among others, and you know
> > he has a lot of stuff in his trees), and it works just fine. There is
> > probably no immediate need for patch grouping nor promote/demote (but we
> > can continue to think about it for the day we'll really need it, of
> > course).
> 
> Yes, I was thinking of Greg KH's workload when I came up with that
> example.  I wonder how he currently deals with that.  I'll have to find
> out.  Anybody know if he subscribes to this list?

Heh, yes, I'm here :)

I think I wrote up how I deal with this somewhere...
Ah, here's the thread:
        http://kerneltrap.org/mailarchive/1/message/59100/thread

Basically, one big series file, multiple subdirs in the patch directory,
and a script that splits them all out into individual sections for
people to play with if they want to.

But, it turns out that the patches I end up with, eventually get
interdepentant in all sorts of wierd ways, so they pretty much have to
be applied in order.  This happens due to api changes in the driver core
a lot...

And I edit that series file a lot, so having quilt try to keep track of
the dependancies would be nice, but _way_ down on my list of things I'd
like to see quilt handle better.

Not to say I don't like quilt.  Not at all, it's great, I wish I had
switched to it sooner.  I have over 250 patches in my tree right now and
quilt handles them just fine.  Without it I would be back to using
bitkeeper :)

thanks,

greg k-h