Re: merge time

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Jul 30, 2007, 03:16 UTC
Message-ID: <alpine.LFD.0.999.0707292011170.4161@woody.linux-foundation.org>
In-Reply-To: <alpine.LFD.0.999.0707292000190.4161@woody.linux-foundation.org>

On Sun, 29 Jul 2007, Linus Torvalds wrote:

Show 5 quoted lines

>
> So in theory, we could pick one particular public kernel.org machine, and 
> use the times as _that_ machine sees it, but the fact is, that isn't how 
> git works. No normal git command will ever show you such a senseless 
> ordering.

So to be constructive, and just tell you what the *sensible* ordering is:

 - get a kernel git clone

 - do "git pull" to update it.

 - do

	gitk ORIG_HEAD..

   to show what the new stuff is after each update, or do something like

	gitk v2.6.23-rc1..

  to show what is new after -rc1 (or "gitk @{2.days.ago}.." to see what 
  is new in _your_ tree in the last two days or whatever).

No commit dates anywhere. Just commit relationships and your *local* views of time.

(Sure, gitk will show you the commit dates too, but they aren't important, since they have no meaning as to whether a commit got merged into 2.6.23-rc1 or not).

		Linus