On Sun, Feb 13, 2011 at 08:35:43PM -0800, Greg KH wrote:
> On Sun, Feb 13, 2011 at 06:24:31PM -0800, Dmitry Torokhov wrote:
> > On Sat, Feb 12, 2011 at 08:07:13AM -0800, Greg KH wrote:
> > > On Fri, Feb 11, 2011 at 11:54:34PM -0800, Dmitry Torokhov wrote:
> > > > On Fri, Feb 11, 2011 at 03:58:28PM -0800, Greg KH wrote:
> > > > >
> > > > > This patch doesn't apply to the .37 stable tree.
> > > > > If someone wants it applied there, please email the backport
> > > > > to [email protected]
> > > > >
> > > >
> > > > It applies if you adjust the paths. You should have just cherry-pick it,
> > > > from mainline, git is smart and follows renames.
> > >
> > > Git is smart, too bad I'm using quilt for the stable queues as git
> > > doesn't work with this development model :(
> > >
> >
> > Have you tried StGIT? I am using it to manage my internal queue - you
> > get flexibility of quilt with power of git.
>
> I tried it a long time ago and it was too slow, but I should try it
> again one of these days.
It is not stgit itself but I think git wants warm cache... First
import used to be painful on my laptop but is not noticeable on my
workstation nor on the laptop now that I have an SSD.
> Even if I did use it, I still start out with
> the "raw" patch from git so if I import it to stgit, it would have had
> the same problem here.
No, if you keep mainline as a branch of your working tree then you
can simply do:
stg pick <mainline_commit_id>
and git goodness will be applied ;)
--
Dmitry
_______________________________________________
stable mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/stable
