All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
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 3.0.6
Date: Mon, 3 Oct 2011 14:26:26 -0700	[thread overview]
Message-ID: <20111003212626.GA24927@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1110032308120.1489@ionos>

On Mon, Oct 03, 2011 at 11:11:12PM +0200, Thomas Gleixner wrote:
> On Mon, 3 Oct 2011, Greg KH wrote:
> 
> > I'm announcing the release of the 3.0.6 kernel.
> > 
> > There was a build error in the radeon driver of the 3.0.5 kernel, so
> > this update is only needed if you have problems building that kernel.
> > 
> > The updated 3.0.y git tree can be found at (NOTE THE ADDRESS CHANGE):
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> 
> That's missing the branch
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git 3.0.y

Oops, sorry, you are right.

> and while I can see the reason to make branches instead of separate
> trees, it's a nightmare when you want to get the 3.0.y tags because
> git insists on downloading the world and some more :(. It's just a one
> time thing, but nevertheless anoying as hell.

Yeah, but now we will not have a ton of different directories, one per
minor release, as it seemed that everyone ended up using the merged tree
anyway.

thanks,

greg k-h

  reply	other threads:[~2011-10-03 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 20:35 Linux 3.0.6 Greg KH
2011-10-03 20:36 ` Greg KH
2011-10-03 21:11 ` Thomas Gleixner
2011-10-03 21:26   ` Greg KH [this message]
2011-10-15 11:56 ` Harald Dunkel
2011-10-15 14:28   ` Harald Dunkel

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=20111003212626.GA24927@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.