On Sun, Nov 05, 2006 at 11:37:08AM -0800, Junio C Hamano
wrote:
> I recall discussing this exact behaviour with Pasky
when he
> added it to Cogito. I think we concluded that it is a
very
> sensible thing to pretend we fetched immediately after
we
> successfully pushed and got the same thing back, and
there is no
> risk of data loss or user confusion, as long as we
catch failure
> from the push and refrain from doing this update, which
Cogito
> did implement correctly when we discussed this.
Is it possible for hooks on the receiving side to change the
tip commit
in some way? For example, the 'update' hook could do some
markup on the
commit message or contents, creating a new commit and using
it instead
of the pushed one; in this case, the sending side ends up
with an
incorrect (and unrelated) SHA1. Is this simply too insane to
worry
about?
-Peff
-
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://vge
r.kernel.org/majordomo-info.html
|