All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Lars Hjemli <hjemli@gmail.com>
Cc: Brian Gernhardt <benji@silverinsanity.com>, git@vger.kernel.org
Subject: Re: git branch --switch?
Date: Tue, 17 Apr 2007 19:27:59 +0200	[thread overview]
Message-ID: <4625039F.7000804@gmail.com> (raw)
In-Reply-To: <8c5c35580704171000g74d8944w7c7b3d07228cac2@mail.gmail.com>

On 04/17/2007 07:00 PM, Lars Hjemli wrote:

> Ok. Then maybe you want to try something like this:
> 
> $ git clone -l -s -n ../linux-2.6 rene
> $ cd rene
> $ git remote add v20
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y
> $ git fetch v20
> 
> This gives you a tracking branch for 2.6.20.y, named as "v20/master".
> That branch can then be used as a starting point for your a, b and c
> branches, like:
> 
> $ git checkout -b a v20/master    # this _will_ take some time...
> 
> After applying some changes on branch a, you can then merge the latest
> changes on the v20-branch like this
> 
> $ git fetch v20
> $ git merge v20/master
> 
> If you want the merge to occur on a separate branch, do this first:
> 
> $ git checkout -b tmp a

Thanks much! This is very useful.

Rene.

  reply	other threads:[~2007-04-17 17:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 13:36 git branch --switch? Rene Herman
2007-04-17 14:21 ` Alex Riesen
2007-04-17 14:29   ` Rene Herman
2007-04-17 14:46   ` Brian Gernhardt
2007-04-17 15:11     ` Alex Riesen
2007-04-17 15:44       ` Rene Herman
2007-04-17 14:31 ` Brian Gernhardt
2007-04-17 15:41   ` Rene Herman
2007-04-17 15:47     ` Rene Herman
2007-04-17 15:55     ` Lars Hjemli
2007-04-17 16:10       ` Rene Herman
2007-04-17 16:50         ` Randal L. Schwartz
2007-04-17 17:03           ` Rene Herman
2007-04-17 17:00         ` Lars Hjemli
2007-04-17 17:27           ` Rene Herman [this message]
2007-04-17 16:24     ` Rene Herman
2007-04-17 16:44       ` Linus Torvalds
2007-04-17 16:55         ` Rene Herman

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=4625039F.7000804@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.