From: Chris Wright <chrisw@sous-sol.org>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Rene Herman <rene.herman@gmail.com>,
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 10:19:08 -0700 [thread overview]
Message-ID: <20070414171908.GU10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <5A4D6434-3DF2-4CC7-B363-260E5F945F72@silverinsanity.com>
* Brian Gernhardt (benji@silverinsanity.com) wrote:
> On Apr 14, 2007, at 4:34 AM, Chris Wright wrote:
> >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
>
> Is HEAD for that repo the most recent stable branch, or (as gitweb
> makes it look) Linus's head. I'd expect a "-stable" repo to point at
> the most recent stable commit, not the most recent development
> commit. And I'd also expect gitweb's summary page to show the
> shortlog for HEAd. One of my assumptions are being broken and I
> don't like it. It leaves me all confused...
As I mentioned. The master branch (HEAD) is Linus' tree, and each
stable tree is on its own branch. You'll find shortlog summarizes the
main branch, so yes, gitweb's summary is a bit confusing based on your
assumptions. This is a new tree and hasn't been publicized until now.
It does make sense to have its head be the newest stable, I'll switch
that around.
thanks,
-chris
next prev parent reply other threads:[~2007-04-14 17:19 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
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 [this message]
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=20070414171908.GU10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=benji@silverinsanity.com \
--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 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.