Re: nicer frontend to get rebased tree?

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Aug 23, 2008, 18:56 UTC
Message-ID: <alpine.LFD.1.10.0808231152250.3363@nehalem.linux-foundation.org>
In-Reply-To: <20080823181827.GA15993@atjola.homenet>

On Sat, 23 Aug 2008, Björn Steinbrink wrote:

Show 8 quoted lines

> 
> So, how would you make it less obscure and unobvious then the current
> method? The current method would be:
> 
> git fetch linux-next
> git checkout linux-next/whatever
> 
> Which seems neither obscure nor unobvious to me...

One thing that I admit we haven't done is _document_ this in some obvious place.

When you know git, it's really fairly obvious and straightforward. But for somebody who doesn't, then _all_ the documentation is really about well-maintained trees that don't rebase. We very much discourage rebasing, and none of the docs even really talk about how to handle it.

The linux-next tree in general is I think not as useful as people think it could be. _I_ think it's been sold as something much bigger and more useful than "it's a tree where you see conflicts early, but you can't actually really _use_ it for anything".

So part of it is not even necessarily about _git_ documentation, but about the documentation for some of the trees that use git, but that aren't really meant for others to then use.

		Linus