From: Willy Tarreau <w@1wt.eu>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [ANNOUNCE] The longterm Linux 2.6.35.14 kernel is released
Date: Tue, 2 Aug 2011 20:55:01 +0200 [thread overview]
Message-ID: <20110802185501.GC32027@1wt.eu> (raw)
In-Reply-To: <87aabraca3.fsf@turtle.gmx.de>
On Tue, Aug 02, 2011 at 08:39:16PM +0200, Sven Joachim wrote:
> > I checked the tree on master, it is uptodate. Don't know why it's
> > not reaching the main git server. Maybe have to wait a bit longer.
>
> I don't think that's the problem, since the v2.6.35.14 tag and the
> commits that lead to it have been at
> git.kernel.org/pub/scm/linux/kernel/git/longterm/linux-2.6.35.y.git for
> at least twelve hours. The problem is that while the tag is there, the
> master branch is still at v2.6.35.13-original. This happens if you just
> "git push v2.6.35.14" without _also_ explicitly pushing the master
> branch. In that case, the commits leading to v2.6.35.14 get pushed (and
> can be fetched with "git fetch -t") but are not on any branch.
>
> Linus himself had already made this mistake at least twice, so it can
> happen to anyone, I guess. :-)
I too made this mistake a few times. However I just checked Andi's tree
on hera and it's OK, master == v2.6.35.14, so possibly this is just a
synchronization issue. Let's wait a bit.
Cheers,
Willy
next prev parent reply other threads:[~2011-08-02 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 21:59 [ANNOUNCE] The longterm Linux 2.6.35.14 kernel is released Andi Kleen
2011-08-02 7:05 ` Sven Joachim
2011-08-02 18:17 ` Andi Kleen
2011-08-02 18:39 ` Sven Joachim
2011-08-02 18:55 ` Willy Tarreau [this message]
2011-08-02 19:03 ` [stable] " Sven Joachim
2011-08-02 18:25 ` Andi Kleen
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=20110802185501.GC32027@1wt.eu \
--to=w@1wt.eu \
--cc=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=svenjoac@gmx.de \
/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.