[MERGE/RFC] Userdoc Driven Design on the Bazaar 2.0 UI

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephen J. Turnbull wrote:
> Neil Martinsen-Burrell writes:
> 
>  > Yes, one can ``echo "git push" > .git/hooks/post-commit`` but that
>  > is much more fussy than ``bzr bind`` and again has the wrong
>  > ordering for integrity.
> 
> I don't understand what you mean by that.  Should I infer that "data
> integrity" requires that the VCS should push the changes, then fetch
> the history back?
> 
> 
> 

If two people are using the same "post commit push to remote" hook, then
if they both commit one of them will fail. They won't find out about
this until after they have already committed. So to get things "back on
track", they'll need to pull from remote, rebase their local changes,
and push it back. And there is no guarantee that in the time you are
rebasing your local changes, the other user hasn't pushed up yet another
commit.

In contrast, with a "bound branch", bzr will refuse the initial commit
if you are out of date. You'll still need to pull the remote changes, etc.

The big thing is that you don't actually need to 'rebase' the commit, as
the commit wasn't really generated. It removes an extra step (not to
mention needing to be aware of the notification that the push failed, etc.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknokfoACgkQJdeBCYSNAAM5fwCfaMS2xJogtCxA/U1Zt/u9r0XQ
A9UAoIi2XpO27HcfE2F5F76JyK4CN/ys
=acBG
-----END PGP SIGNATURE-----