Linus Torvalds wrote:
quoted text
> On Sat, 26 Apr 2008, Stefan Richter wrote:
>> Well, the need to amend single patches --- and folding the amendment in before
>> mainline submission to correct important problems of the first shot --- is
>> something which happens all the time.
> 
> .. and you simply SHOULD NOT PUBLICIZE the tree before it has gotten to a 
> reasonable point.

I always aim for keeping the one subsystem git tree which I maintain in 
reasonable shape.  Including its -mm and -next feeding branches.

quoted text
> Keep the rough-and-not-ready thing that is being discussed as patches on 
> lkml as your own working tree, and just don't expose it as a public git 
> branch. You can't do any sane discussion over git anyway - if things are 
> being actively worked-on among people, you'd be passing patches around as 
> emails etc.

Sometimes I want problem reporters to test more than a single patch.  In 
these cases, I refer them to patch kits and quilt queues which I 
maintain independently of linux1394-2.6.git; I almost never ask testers 
to try linux1394-2.6.git.

linux1394-2.6.git has been, and still is, first and foremost my 
submission branch to -mm.  And I have high expectations of what I submit 
to -mm.  But sometimes something turns out to be a bad idea after all 
_long after_ I and the reviewers and testers thought it would be fine.

Besides, the care that I take with my submissions to -mm also does not 
change the fact that I submit in different order to you than to -mm.
(As mentioned, reordering could be done to some degree with a respective 
number of branches.  I don't do it this way currently.)
-- 
Stefan Richter
-=====-==--- -=-- ==-=-
http://arcgraph.de/sr/
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/