From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: git@vger.kernel.org
Subject: Re: nicer frontend to get rebased tree?
Date: Fri, 22 Aug 2008 13:29:39 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808221301300.3487@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808221233100.3487@nehalem.linux-foundation.org>
On Fri, 22 Aug 2008, Linus Torvalds wrote:
>
> So what you can do is to "git fetch" it (to download it), and then "git
> checkout" to create a temporary checkout. That's pretty much all you can
> do with linux-next.
.. oh, and you can also do a throw-away branch and test what a merge would
look like when merged into linux-next.
Basically there's a few sane sequences you can do with linux-next:
- They all basically start with "fetch and test":
# This obviously assumes you have set up 'linux-next' as a branch
# earlier by either editing .git/config or using 'git remote add'
# or something
git fetch linux-next
git checkout linux-next/master
.. this will create a _temporary_ branch ("detatched head") ..
.. you can now compile, install, boot this state ..
repeat as necessary, but never actually do anything else with that
detached branch (do a "git checkout master" to get back to a sane
state)
and after that you can do some things:
- You can do throw-away work on that temporary branch: you can fix up
crap when it doesn't compile etc, but you should always remember that
it's purely throw-away, beacuse all of linux-next is throw-away, and
gets re-created from scratch each time.
In particular, one useful "throw-away" thing to do is to test what
would happen if all the crud on linux-next is merged with whatever you
have done youself. So assuming you're still on that throw-away branch
(aka "detached head": "git branch" will say "* (no branch)" is your
current branch), you can do things like
git merge master
to merge in your own work on top of linux-next, but as a total
throw-away (which is what you want: you can never use the state for
anything else anyway, and you do _not_ want to pollute your real work
in "master" by merging in the throw-away linux-next into that!)
but what you should _never_ do is to forget that you're on the throw-away
branch, and do any real development.
Linus
next prev parent reply other threads:[~2008-08-22 20:31 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 [this message]
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
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.0808221301300.3487@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--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).