From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Andi Kleen <andi@firstfloor.org>, git@vger.kernel.org
Subject: Re: nicer frontend to get rebased tree?
Date: Sat, 23 Aug 2008 11:56:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808231152250.3363@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080823181827.GA15993@atjola.homenet>
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
next prev parent reply other threads:[~2008-08-23 18:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 17:46 nicer frontend to get rebased tree? Andi Kleen
2008-08-22 17:55 ` Linus Torvalds
2008-08-22 18:27 ` Andi Kleen
2008-08-22 19:36 ` Linus Torvalds
2008-08-22 20:11 ` Paolo Ciarrocchi
2008-08-22 20:33 ` Linus Torvalds
2008-08-22 20:36 ` Björn Steinbrink
2008-08-22 20:46 ` Paolo Ciarrocchi
2008-08-22 20:29 ` Linus Torvalds
2008-08-22 21:23 ` Junio C Hamano
2008-08-23 7:10 ` Andi Kleen
2008-08-23 9:24 ` Paolo Bonzini
2008-08-23 16:36 ` Andi Kleen
2008-08-23 23:00 ` Paolo Bonzini
2008-08-23 15:55 ` Linus Torvalds
2008-08-23 16:45 ` Andi Kleen
2008-08-23 17:58 ` Linus Torvalds
2008-08-25 9:36 ` Ingo Molnar
2008-08-23 18:18 ` Björn Steinbrink
2008-08-23 18:56 ` Linus Torvalds [this message]
2008-08-23 20:08 ` Björn Steinbrink
2008-08-23 21:38 ` Documentating branches (was: nicer frontend to get rebased tree?) Marius Vollmer
2008-08-23 22:17 ` Miklos Vajna
2008-08-23 22:30 ` Documenting branches Marius Vollmer
2008-08-23 22:18 ` Documentating branches Marius Vollmer
2008-08-22 17:56 ` nicer frontend to get rebased tree? Avery Pennarun
2008-08-22 18:31 ` Andi Kleen
2008-08-22 19:03 ` Paolo Ciarrocchi
2008-08-22 19:34 ` Jakub Narebski
2008-08-23 7:15 ` Andi Kleen
2008-08-23 8:52 ` Paolo Ciarrocchi
2008-08-23 9:21 ` Jakub Narebski
2008-08-23 16:53 ` Andi Kleen
2008-08-23 21:04 ` Paolo Ciarrocchi
2008-08-23 21:52 ` Linus Torvalds
2008-08-23 22:09 ` Paolo Ciarrocchi
2008-08-23 22:13 ` Björn Steinbrink
2008-08-24 0:30 ` Junio C Hamano
2008-08-23 22:49 ` Jakub Narebski
2008-08-23 23:01 ` Theodore Tso
2008-08-23 23:01 ` A proposed solution (Was: nicer frontend to get rebased tree?) Theodore Tso
2008-08-22 20:11 ` nicer frontend to get rebased tree? Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.10.0808231152250.3363@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=B.Steinbrink@gmx.de \
--cc=andi@firstfloor.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).