git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roy Lee <roylee17@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: How to add daily tags for a central repo?
Date: Tue, 1 Jun 2010 15:55:50 +0800	[thread overview]
Message-ID: <AANLkTim02FQ3BfV88iylMqbHA5sBbJvp5TmWg52OXCzn@mail.gmail.com> (raw)
In-Reply-To: <4C04AC1E.7040502@drmicha.warpmail.net>

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

  reply	other threads:[~2010-06-01  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  5:21 How to add daily tags for a central repo? roylee17
2010-06-01  6:43 ` Michael J Gruber
2010-06-01  7:55   ` Roy Lee [this message]
2010-06-01  8:05     ` Michael J Gruber
2010-06-01  8:25       ` Roy Lee
2010-06-01  8:52         ` Michael J Gruber
2010-06-01  9:45           ` Roy Lee
2010-06-01 22:20             ` Ilari Liusvaara
2010-06-02  4:40             ` Junio C Hamano
2010-06-02  7:55               ` Roy Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTim02FQ3BfV88iylMqbHA5sBbJvp5TmWg52OXCzn@mail.gmail.com \
    --to=roylee17@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).