From: Rene Herman <rene.herman@gmail.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Nish Aravamudan <nish.aravamudan@gmail.com>,
Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [stable] Linux 2.6.22.1
Date: Fri, 13 Jul 2007 01:03:57 +0200 [thread overview]
Message-ID: <4696B35D.1030808@gmail.com> (raw)
In-Reply-To: <20070712185219.GR4306@sequoia.sous-sol.org>
On 07/12/2007 08:52 PM, Chris Wright wrote:
> Nish, I think you might be the only user ;-) I never figured out a nice
> way to do this w/out having a coherency issue (well, triggers aside).
> Ideally git would allow for something more transparent than alternatives,
> actual moving view to another tree. It's possible with links, but that
> seems just dirty. Short of that, do folks find the tree useful? If so,
> I can work on some better automation to keep it up-to-date.
I tried this tree a while ago but at the time it had a problem with tags
(http://lkml.org/lkml/2007/4/14/177). I just recloned and see that's now
fixed...
I'm rolling my own since then though. Not sure, but perhaps it's interesting
to someone: when Linus tags a release from his repo I branch of the -stable
branch myself:
$ git checkout -b v22 v2.6.22
and then (following advice from Junio Hamano) add the following stanza to
.git/config:
===
[branch "v22"]
remote = linux-2.6.22.y
merge = refs/heads/master
[remote "linux-2.6.22.y"]
url =
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.22.y.git
fetch = refs/heads/master
===
(the url = is one line, but is wrapping).
When on this v22 branch, a simple "git pull" then updates from the stable
tree. It's been working nicely for me. The manual .git/config editing is a
little awkard perhaps but for all I know I could do so via some well-chosen
git commands.
Rene.
next prev parent reply other threads:[~2007-07-12 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 20:06 Linux 2.6.22.1 Greg KH
2007-07-10 20:06 ` Greg KH
2007-07-12 18:35 ` Nish Aravamudan
2007-07-12 18:41 ` [stable] " Greg KH
2007-07-12 18:46 ` Nish Aravamudan
2007-07-12 18:52 ` Chris Wright
2007-07-12 19:08 ` Nish Aravamudan
2007-07-12 23:02 ` Domenico Andreoli
2007-07-12 23:03 ` Rene Herman [this message]
2007-07-13 6:16 ` Bryan Wu
2007-07-13 6:16 ` Greg KH
2007-07-13 6:28 ` Bryan Wu
2007-07-13 6:34 ` Linus Torvalds
2007-07-13 6:51 ` Chris Wright
2007-07-13 6:58 ` Bryan Wu
2007-07-13 6:47 ` Adrian Bunk
2007-07-13 19:52 ` Greg KH
2007-07-14 0:44 ` H. Peter Anvin
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=4696B35D.1030808@gmail.com \
--to=rene.herman@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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