git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Rene Herman <rene.herman@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	git@vger.kernel.org
Subject: Re: GIT and the current -stable
Date: Sat, 14 Apr 2007 00:21:06 -0700	[thread overview]
Message-ID: <20070414072106.GA6344@kroah.com> (raw)
In-Reply-To: <7vfy73bhik.fsf@assigned-by-dhcp.cox.net>

On Fri, Apr 13, 2007 at 11:24:19PM -0700, Junio C Hamano wrote:
> Rene Herman <rene.herman@gmail.com> writes:
> 
> > 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 think adding these lines to .git/config would do the trick,
> after you have done the "checkout -b v2.6.20 v2.6.20" step:
> 
> [branch "v2.6.20"]
> 	remote = stable
> 	merge = refs/heads/master
> [remote "stable"]
> 	url = git://git.kernel.org/.../stable/linux-2.6.20.y.git
> 	fetch = refs/heads/master
> 
> provided if stable team forks v2.6.20.y history off of Linus's
> v2.6.20.

Yes, we do branch off Linus's tree for each of the different .y
releases.

Some people have asked us to keep all of the different .y branches in
the same git tree, but for now we have been using different repositories
on kernel.org to keep things simpler for the majority of people who do
not fully understand how to use the branching features of git (myself
included in that category at times, I've messed up merging to different
branches too many times...)

> With the above configuration, anytime you say "git pull" while
> on your v2.6.20 branch will fetch from "stable" and merge their
> 'master' branch in your current branch (i.e. v2.6.20 branch).

That's really cool, thanks for pointing out how to do it.

thanks,

greg k-h

  parent reply	other threads:[~2007-04-14  7:20 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 [this message]
2007-04-14 17:34   ` Linus Torvalds
2007-04-14 18:45     ` Gerb Stralko
2007-04-14  8:34 ` Chris Wright
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=20070414072106.GA6344@kroah.com \
    --to=greg@kroah.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --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).