On Sat, 26 Apr 2008, Sam Ravnborg wrote:
quoted text
> 
> It also depends on whare you are located in the dependency tree.

Absolutely.

quoted text
> Being kbuidl maintainer I have very few people that actually pull me git 
> tree (except from -mm and -next). So I rebase at will and have so far 
> not got a single complaint from anyone pulling my tree.

I agree. Some trees are so specific (and/or simply don't have enough 
patches in them) that it simply doesn't matter if two different people 
pull the same tree. Even if it might end up causing some duplication of 
commits (because the pulled tree might end up being then pulled further), 
it's not a big deal if it's rare.

In fact, we have always had duplicated commits even when they are passed 
around as email - just because perhaps two different trees simply needed 
the same fix, and rather than wait for it, they both integrated it (and 
then when they get merged, the same patch exists twice in the history, 
just with different committer info etc).

So yeah, rebasing ends up being really convenient if you really don't 
expect to have any other "real" end users than eventually being pulled 
into my tree (or, even more commonly, and when rebasing is *really* 
convenient: when it's just you keeping track of your own private patches 
in your own private tree and don't know if they will *ever* go upstream at 
all).

quoted text
> But people like Davem and Ingo sits much higher in the dependency chain
> and thus they have a very different set of users and thus a different
> set of problems to take into account.

Yes. David has changed his workflow to accomodate others, while Ingo still 
does the rebasing (and it works out because nobody else works on his trees 
using git).

			Linus
--
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/