linux-kernel - Re: [GIT PATCHES] kbuild.git updates for 2.6.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20060925184035.GA2788@uranus.ravnborg.org>
Date:	Mon, 25 Sep 2006 20:40:35 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Andrew Morton <akpm@...l.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCHES] kbuild.git updates for 2.6.19

On Sun, Sep 24, 2006 at 07:15:25PM -0700, Linus Torvalds wrote:
> 
> 
> On Sun, 24 Sep 2006, Sam Ravnborg wrote:
> >
> > kbuild updates for 2.6.19.
> > 
> > Please pull from:
> > 
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git
> 
> Btw, this shows an irritating bug in your setup: your computer has its 
> clock set wildly incorrectly.
> 
> Git doesn't really _care_, but if you look at gitweb at this time, it will 
> annotate all the commits I pulled from you as being "right now", because 
> your computers clock was set several hours into the future, and thus your 
> timestamps are crap.
> 
> Please fix. The "author" times are correct (they get taken from the emails 
> or from the original commit that got cherry-picked, depending on how you 
> did things), but look for example at commit 5026b38c:
> 
> 	author	Randy Dunlap <rdunlap@...otime.net>
> 		Fri, 22 Sep 2006 19:37:56 +0000 (12:37 -0700)
> 	committer	Sam Ravnborg <sam@...tun.ravnborg.org>
> 		Mon, 25 Sep 2006 11:33:04 +0000 (13:33 +0200)
> 
> and I can tell you that you sure as hell didn't commit that on Monday, 
> September 25, at 11:33 UTC (or 13:33 in +0200), because right now it's 
> 2:13 AM in UTC, and the date your commit got marked for is still more than 
> nine hours in the future (and was further off when you did it).
> 
> I'd suggest running NTP, or at least checking that your date is even 
> _remotely_ correctly set on your computer ;)

Fixed - thanks!

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/