public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Arnd Hannemann <arnd@arndnet.de>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.32.59
Date: Sun, 18 Mar 2012 08:17:53 -0700	[thread overview]
Message-ID: <20120318151753.GA26492@kroah.com> (raw)
In-Reply-To: <20120318132855.GK17033@1wt.eu>

On Sun, Mar 18, 2012 at 02:28:55PM +0100, Willy Tarreau wrote:
> Hi Arnd,
> 
> On Sun, Mar 18, 2012 at 02:22:46PM +0100, Arnd Hannemann wrote:
> > Hi,
> > 
> > Am 17.03.2012 14:09, schrieb Willy Tarreau:
> > 
> > > The updated 2.6.32.y git tree can be found at:
> > >    git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-2.6.32.y
> > >   http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-2.6.32.y
> > > 
> > > The tree can be browsed on the gitweb interface:
> > >   http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/heads/linux-2.6.32.y
> > 
> > Neither any commit after 2.6.32.58 nor the tag v2.6.32.59 seems to be available in the public git tree, yet.
> > Forgot to push?
> 
> Greg was not available for the final push when I sent the announce yesterday
> and I made a mistake in the pull request I sent him, further delaying the
> update. This will be sorted out soon, don't worry.

Sorry for the delay, they are now pushed out and should show up on the
public mirrors within minutes now.

greg k-h

  reply	other threads:[~2012-03-18 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17 13:09 Linux 2.6.32.59 Willy Tarreau
2012-03-18 11:20 ` Nikola Ciprich
2012-03-18 11:59   ` Willy Tarreau
2012-03-18 13:22 ` Arnd Hannemann
2012-03-18 13:28   ` Willy Tarreau
2012-03-18 15:17     ` Greg KH [this message]
2012-03-18 16:30       ` Willy Tarreau

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=20120318151753.GA26492@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndnet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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