Messages in this thread |  | | | Date | Tue, 12 Feb 2008 17:16:03 -0800 (PST) | | Subject | Re: Announce: Linux-next (Or Andrew's dream :-)) | | From | David Miller <> |
From: Andrew Morton <akpm@linux-foundation.org>
Date: Tue, 12 Feb 2008 16:37:42 -0800
> Well there's a case in point. rcupdate.h is not a part of networking, and
> it is random tree-wandering like this which causes me problems and which
> will cause Stephen problems.
>
> Now, I don't know which tree "owns" rcupdate.h but it ain't networking.
> Probably git-sched.
>
> Nothing in networking depends upon that change (which has a typo in the
> comment, btw) hence it can and should have gone through
> whichever-tree-owns-that-file.
>
> For Stephen's sake: please.
At least thie time I did make sure that change got posted to
linux-kernel and got properly reviewed by the de-facto maintainer
(Paul McKenney). :-)
I'll toss it.
But how do I do that using GIT without rebasing and without
having this ugly changeset and revert in there?
That's the thing I want answered, and although Al claims it does,
git cherry-pick does not seem to do what I want either.
|  |