On Tue, Jun 1, 2010 at 4:52 PM, Michael J Gruber
<git@xxxxxxxxxxxxxxxxxxxx> wrote:
> Roy Lee venit, vidit, dixit 01.06.2010 10:25:
>> On Tue, Jun 1, 2010 at 4:05 PM, Michael J Gruber
>> <git@xxxxxxxxxxxxxxxxxxxx> wrote:
>>> Roy Lee venit, vidit, dixit 01.06.2010 09:55:
>>>> Hi Michael,
>>>>
>>> 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".
>>
>> Does this mean the tagging must be done on the server?
>
> Yes.
>
>> Is there any way to query this information from a client repo,
>> do the tagging locally, and than push the tag back to the server?
>
> No.
>
> This answer assumes that what you want to do is the following:
>
> * Create a tag for the state of a ref (such as HEAD) on the central repo
> at a specific date and time.
Yes, for the daily build stuff.
> No client can know this. Reflogs are local. The point of your tagging
> (as I understand it) is to create an authoritative date based tag, and
> only the central repo has the necessary info.
>
> If you want to do something different you should say so ;) But note that
> committer and author dates are completely bogus from the point of view
> of "was in the central repo at a certain date", they have nothing to do
> with that.
>
> Michael
I've been using reflog locally for some time, but never thought that
it could be used in this way -- combining with timespec to get the
timestamps of updates to the server. :)
The only problem now is that the tag creator might not have the access
to shell on the central server. To grant the shell access for the tag creator
may be a quick way to circumvent this. But I think I'll try if git can export
the reflog to the client in a native way or with some trickery.
Thank you so much, Michael.
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