lkml.org 
[lkml]   [2008]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux 2.6.16.58
On Thu, 17 Jan 2008, Willy Tarreau wrote:
> On Thu, Jan 17, 2008 at 11:47:55PM +0200, Adrian Bunk wrote:
> > On Thu, Jan 17, 2008 at 10:12:05PM +0100, Willy Tarreau wrote:
> > > 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...
>
> Maybe he did this locally (Linus showed me that local FS cloning disables
> a lot of tests). Or maybe it could work for some pulls :-/ Definitely a
> weird issue anyway!

Err... I managed to do it for thinkpad-acpi's merge tree too, a lot of time
ago. So it was somehow possible to get it through the anonymous git server,
probably through the tag. What I do know is that I usually send head's up
email when I notice something like this, and I find it strange that you
didn't get one from me at that time... but I may have forgotten to send it
at that time.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh


\
 
 \ /
  Last update: 2008-01-17 23:05    [W:1.551 / U:0.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site