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?
Or any alternatives for developer to query this information.
Regards,
Roy
--
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