From: Rene Herman <rene.herman@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>, git@vger.kernel.org
Subject: GIT and the current -stable
Date: Sat, 14 Apr 2007 07:36:02 +0200 [thread overview]
Message-ID: <46206842.80203@gmail.com> (raw)
Good day.
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
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.
Is this possible? Do I want it to be? Comments like "work like this instead"
welcome as well; figuring out what the heck it is that I want from git seems
to be one of the most difficult questions to answer...
Currently using git 1.5.0.4.
Rene.
next reply other threads:[~2007-04-14 5:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 5:36 Rene Herman [this message]
2007-04-14 6:24 ` GIT and the current -stable 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
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=46206842.80203@gmail.com \
--to=rene.herman@gmail.com \
--cc=git@vger.kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@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).