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

[Greg KH]

On Fri, Jun 03, 2005 at 12:18:36PM -0500, Josh Boyer wrote:
> > 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 ;).

Heh, ok, you asked.  Possibly some of these are just me not knowing how
to use quilt better.  If so, please just point me at the related
documentation and I'll shut up :)

 - Handle patches that are already applied in the base tree (meaning,
   let the user know, like patch does with the "this patch is already
   applied..." message it puts up at you.  Instead, today we get a "all
   hunks failed" type message and it's up to the user to realize that
   this really isn't a merge issue.
 - Fix the bash errors of broken pipes.  Yes, Jean has pointed out how
   to rebuild bash to fix this issue, but as not all users know how to
   do this, it's not that nice.
 - let 'delete' work on the next patch in the series (the one not yet
   applied) without having to remember what that filename of the patch
   is.  Yeah, it's a minor nit...
 - Chris Mason has a nice wrapper script to quilt (called qa) that helps
   with applying long series of patches.  Merge some of that
   functionality into the base quilt code.

That's all I can think off right now.  See I told you they were minor
things...

thanks,

greg k-h