From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Scott Sandler <scott.m.sandler@gmail.com>
Cc: Nasser Grainawi <nasser@codeaurora.org>,
Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Git push race condition?
Date: Tue, 25 Mar 2014 15:03:29 +0100 [thread overview]
Message-ID: <vpqvbv2pe8e.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAAyEjTPtaKExJJSc3yrxVNzx0DmOyeUFH-Uxz3dn0iezqc5VKA@mail.gmail.com> (Scott Sandler's message of "Tue, 25 Mar 2014 09:45:20 -0400")
Scott Sandler <scott.m.sandler@gmail.com> writes:
> Is there a hook or cron job that updates or gcs this repository or any
> refs? No. No cron jobs touching the repo at all, and all the hooks are
> read-only.
If you activated the reflog, you can double-check that. Running git
reflog on the server should give you something like this:
$ git reflog show master
bf40764 (HEAD, master) master@{0}: push
2c4fc6d master@{1}: push
e72211a master@{2}: push
...
It should be possible to check the reflog for non-fast forward. I don't
find an obvious way, but a script going through the sha1 list and
checking that each line is an ancestor of the previous should be easy.
I can't exclude the hypothesis of a bug in Git, but my feeling is that
there's an issue with your setup.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-03-25 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 19:18 Git push race condition? Scott Sandler
2014-03-24 19:44 ` Matthieu Moy
2014-03-24 20:01 ` Scott Sandler
2014-03-24 22:09 ` Matthieu Moy
2014-03-24 22:44 ` Junio C Hamano
2014-03-24 21:16 ` Ævar Arnfjörð Bjarmason
2014-03-24 21:29 ` Scott Sandler
2014-03-24 22:51 ` Jeff King
2014-03-24 22:54 ` Jeff King
2014-03-24 22:59 ` Nasser Grainawi
2014-03-25 13:45 ` Scott Sandler
2014-03-25 14:03 ` Matthieu Moy [this message]
2014-03-25 14:16 ` Scott Sandler
2014-03-25 14:22 ` Matthieu Moy
2014-03-25 14:57 ` Jeff King
2014-04-10 19:14 ` Scott Sandler
2014-04-11 7:46 ` Matthieu Moy
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=vpqvbv2pe8e.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=nasser@codeaurora.org \
--cc=peff@peff.net \
--cc=scott.m.sandler@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.