Accessing the reflog remotely

Hi,

I guess the answer is "no", but I'll still ask in case ...

Is it possible to access the reflog of a remote repository other than logging into this repository?

My use-case is the following: I want to checkout "the last revision pushed in master on ssh://host/repo/ on day D at midnight" (to fetch the project of my students ;-) ). If it were locally, I'd do

  git checkout 'origin/master@{Nov 3 00:00:00}'

But this tells me where _my_ local master was on that date (i.e. the last revision I had pulled).

So, the best I can think of is:

ssh host 'cd /repo/ ; git tag final-version "master@{Nov 3 00:00:00}"' git fetch --tags git checkout tags/final-version

Is there a better way?

Thanks,

Matthieu Moy provò:

At least you can avoid the tag:

git checkout `ssh host 'GIT_DIR=/repo/ git rev-parse "master@{Nov 3 00:00:00}"'`

On Nov 4, 2009, at 10:35 AM, Matthieu Moy wrote:

Keep in mind that bare repos don't have reflogs by default, so unless you enabled the reflog manually there is none.

tom

On Wed, 4 Nov 2009, Matthieu Moy wrote:

No.

You could checkout the first revision which committer's date is older than midnight. Of course that means you have to trust that students didn't mess up with time stamps.

Nicolas

Nicolas Pitre <nico@fluxnic.net> writes:

Not only that: they could have commited something the day before, and pushed it the day after. In the particular case I have in mind, the deliverable is an intermediate one, and we insist a lot on testing, so the senario is not unlikely: commit dangerous code the day of the deadline, and push it the day after. So, the reflog is definitely the answer here.

But thanks anyway!

Heya,

On Wed, Nov 4, 2009 at 10:35, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

I think your best bet here would be to either run a cronjob at the target time that tags all submissions, or to deny pushes after the target time with a pre-push hook.

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

This won't solve your problem but I'll mention it anyway as it may be related.

A distribution point repository like this is often bare, and reflogs are not enabled in bare repositories (primarily due to my stupidity^Wbeing overly cautious---I was very skeptical about reflogs when we introduced it). It may make sense to enable reflogs everywhere by default in some major version bump.

Also a distribution point repository is often served by gitweb and it would be really nice if there were an option to allow its summary view to show commits annotated with reflog entries, e.g.

    ----------------------------------------------------------------
    2 days ago          JCH Merge branch 'maint'
    (pushed 6 hrs ago)
    ----------------------------------------------------------------
    2 days ago          DVL Makefile: add compat/bswap.h to LIB_H
    ----------------------------------------------------------------
    3 days ago          JCH Revert "Don't create the $GIT_DIR/branches directory on init"
    (pushed 60 hours ago)
    ----------------------------------------------------------------
    4 days ago          JCH fixup tr/stash-format merge
    ----------------------------------------------------------------
        ...

Junio C Hamano <gitster@pobox.com> writes:

Thanks for reminding it (I knew it, but I could very well have forgotten at the last minute ...) :-).