git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Rene Herman <rene.herman@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	git@vger.kernel.org
Subject: Re: GIT and the current -stable
Date: Sat, 14 Apr 2007 01:34:10 -0700	[thread overview]
Message-ID: <20070414083410.GU6602@sequoia.sous-sol.org> (raw)
In-Reply-To: <46206842.80203@gmail.com>

* Rene Herman (rene.herman@gmail.com) wrote:
> Stumbling around with git here. I'd like to use git to efficiently track 
> the current -stable as well as -current. Say, my local tree is a clone of 
> Linus current:
> 
> git clone \ 
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git local
> 
> I then branch off a 2.6.20 branch:
> 
> cd local
> git checkout -b v2.6.20 v2.6.20
> 
> to now update to the current -stable I could do:
> 
> git pull \ 
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.git

I've already put a tree like this up on kernel.org.  The master branch
is Linus' tree, and there's branches for each of the stable releases
called linux-2.6.[12-20].y (I didn't add 2.6.11.y).

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=summary

> each time that a new -stable is released. Rather though, I'd like a simple 
> "git pull" to do this while on this branch while a "git pull" while back on 
> the master branch pulls from the originally cloned Linus repo again.

You have to be careful with pull.  It will always want to merge onto your
current branch.

thanks,
-chris

  parent reply	other threads:[~2007-04-14  8:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-14  5:36 GIT and the current -stable Rene Herman
2007-04-14  6:24 ` Junio C Hamano
2007-04-14  7:13   ` Rene Herman
2007-04-14  7:21   ` Greg KH
2007-04-14 17:34   ` Linus Torvalds
2007-04-14 18:45     ` Gerb Stralko
2007-04-14  8:34 ` Chris Wright [this message]
2007-04-14  8:54   ` Rene Herman
2007-04-14 23:13     ` Rene Herman
2007-04-15  0:23       ` Julian Phillips
2007-04-14 15:15   ` Brian Gernhardt
2007-04-14 17:19     ` Chris Wright
2007-04-14 17:23       ` Brian Gernhardt
2007-04-14 17:31         ` Chris Wright
2007-04-14 19:07       ` Julian Phillips
2007-04-14 11:56 ` Uwe Kleine-König

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=20070414083410.GU6602@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@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 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).