On Sun, 29 Jul 2007, Linus Torvalds wrote:
>
> 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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
