On Mon, 19 Sep 2005, Petr Baudis wrote:
quoted text
> 
> I think it should actually never happen, updating the references should
> always come as the last thing in the push (or pull, for that matter)
> process.

It happens when you have several layers of non-git-aware stuff in between.

On kernel.org it happens occasionally with the mirroring, for example. I 
push something out while a mirror event is active, and the mirroring ends 
up finding the refs before the objects.

The same could happen with a write-back distributed networked filesystem,
for example (not NFS, which is synchronous in metadata, but some other
level of non-git-aware thing that doesn't necessarily maintain write
ordering).

In general, git does the right thing for anything that honors write 
ordering, but the fact is, there are things that don't.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html