Roy Lee venit, vidit, dixit 01.06.2010 09:55:
> Hi Michael,
>
>>
>> Having these tags seems strange to me. Imagine someone pushing a patch
>> series one-by-one around midnight, or pushing a commit and, shortly
>> after, a fixup. You'll end up with a tag pointing to a commit in the middle.
>>
>> The commit time is totally unreliable, as you noticed, also because
>> authors may commit locally, then push later.
>>
>> That being said, if you're really interested in the state of a branch on
>> the central server at a certain point in time it's easiest to enable
>> reflogs on the central repository (by setting core.logAllRefUpdates or
>> enabling individually) and to tag the commit HEAD@{datetimespec} (or
>> branchname@...). No need for cloning.
>>
>> Cheers,
>> Michael
>>
>
> This is what I'm looking for. Thanks a lot.
>
> But I have another question:
> How to use the refspec to refer to the reflogs?
Well, as I wrote: HEAD@{datetimespec} for the HEAD,
branchname@{datetimespec} for a branch "branchname". datetimespec is
decribed in git rev-parse's manpage but can be what you'd think (e.g.
"date time") and more ("yesterday").
If you really want to inspect the reflog (not the commits listed in the
reflog) use "git log -g" or, unsurprisingly, "git reflog".
> Or any alternatives for developer to query this information.
The reflog is local to the repo, which is why you would create tags on
the central repo based on the reflog there, if that is your "trusted
time and push reference source".
Cheers,
michael
--
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