Re: nicer frontend to get rebased tree?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Sat, 23 Aug 2008, Björn Steinbrink wrote:
> 
> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux