From: Adrian Bunk <bunk@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Jiri Kosina <jikos@jikos.cz>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.58
Date: Thu, 17 Jan 2008 23:47:55 +0200 [thread overview]
Message-ID: <20080117214755.GB28233@does.not.exist> (raw)
In-Reply-To: <20080117211205.GE8953@1wt.eu>
On Thu, Jan 17, 2008 at 10:12:05PM +0100, Willy Tarreau wrote:
> Hi Adrian,
>
> On Thu, Jan 17, 2008 at 10:34:16PM +0200, Adrian Bunk wrote:
> > do you insist on hearing the truth ("Sorry, I forgot to push."), or can
> > I tell you "I just wanted to see whether anyone notices." instead? ;-)
>
> :-)
>
> I think we should intentionally do this test once in a while. Two days
> ago I was informed that 2.6.20.21 (the latest 2.6.20 I pushed 3 months
> ago) was not clonable nor pullable due to a problem with the HEAD
> pointing to latest tag instead of latest commit. Since the error was
> also present in my local tree, I'm certain that it remained there
> unnoticed for 3 months !
According to git [1] Ralf merged 2.6.20.21 on 2007-10-18 into the 2.6.20
branch of his mips tree, so it must have been somehow possible...
> Cheers,
> Willy
cu
Adrian
[1] http://www.linux-mips.org/git?p=linux.git;a=shortlog;h=linux-2.6.20-stable
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-17 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 22:18 Linux 2.6.16.58 Adrian Bunk
2008-01-16 16:04 ` Jiri Kosina
2008-01-16 20:14 ` Willy Tarreau
2008-01-17 20:34 ` Adrian Bunk
2008-01-17 21:12 ` Willy Tarreau
2008-01-17 21:47 ` Adrian Bunk [this message]
2008-01-17 21:32 ` Willy Tarreau
2008-01-17 22:02 ` Henrique de Moraes Holschuh
2008-01-17 21:48 ` Willy Tarreau
2008-01-18 12:24 ` Henrique de Moraes Holschuh
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=20080117214755.GB28233@does.not.exist \
--to=bunk@kernel.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@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