public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net
Subject: Re: Linux 2.6.35.6
Date: Sun, 26 Sep 2010 18:31:52 -0700	[thread overview]
Message-ID: <20100927013152.GA21139@suse.de> (raw)
In-Reply-To: <AANLkTikHtuXhMtjudLTUMPR7uL9eGGePUP93MqFLTfb5@mail.gmail.com>

On Mon, Sep 27, 2010 at 04:00:51AM +0300, Felipe Contreras wrote:
> Hi,
> 
> On Mon, Sep 27, 2010 at 3:36 AM, Greg KH <gregkh@suse.de> wrote:
> > I'm announcing the release of the 2.6.35.6 kernel.
> >
> > All users of the 2.6.35 kernel series must upgrade.
> >
> > The updated 2.6.35.y git tree can be found at:
> > ?? ?? ?? ??git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.35.y.git
> > and can be browsed at the normal kernel.org git web browser:
> > ?? ?? ?? ??http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.35.y.git;a=summary
> 
> I usually do 'git fetch' to get new changes in all my repos, however,
> this one seems to be a bit different; there's no branch. Since there's
> no branch, 'git fetch' doesn't retrieve the tags.
> 
> Can you add a 'master' branch that points to the latest tag? That
> would make things easier for other people, specially the ones that
> just do 'git pull'.

I don't understand, this works for me this way, the master branch _is_
the latest version at all times.  Did you just need to wait a few
minutes to have the mirror catch up?

thanks,

greg k-h

  reply	other threads:[~2010-09-27  1:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  0:36 Linux 2.6.35.6 Greg KH
2010-09-27  0:36 ` Greg KH
2010-09-27  1:00 ` Felipe Contreras
2010-09-27  1:31   ` Greg KH [this message]
2010-09-27 17:05     ` Felipe Contreras
2010-09-27 16:32 ` tmhikaru
2010-09-27 17:54   ` Greg KH
2010-09-27 19:09     ` tmhikaru
2010-09-27 19:51   ` Florian Mickler
2010-09-27 23:39     ` tmhikaru
2010-09-28  4:45       ` tmhikaru
2010-09-28  6:35       ` Florian Mickler
2010-09-28 19:03         ` tmhikaru
2010-09-29  7:29           ` Florian Mickler
2010-09-29 11:02             ` tmhikaru
2010-09-29 11:33               ` Miguel Ojeda
2010-09-29 11:52               ` Florian Mickler
2010-09-29 12:19                 ` Florian Mickler
2010-09-30  1:33                 ` tmhikaru
2010-09-30  5:29                   ` Florian Mickler
2010-09-30  7:38                     ` tmhikaru

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=20100927013152.GA21139@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=felipe.contreras@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --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