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

[Josh Boyer]

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

Oh, good :)

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

I remember seeing that now.  Thanks.

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

Interdependant between different "patchsets"?  I could see how that
happens.  I guess my proposal wouldn't be able to deal with that and would
still require the user to know what order to apply the series files in.
But I don't consider that too big of a deal.  I mean, the user has to have
_some_ knowledge of what needs to be done :).

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

OK, now you've piqued my interested.  What is your list of things that
you'd like to see quilt handle better?  You can't just leave us hanging
like that ;).

thx,
josh