Automate push after commit?

[Robert Collins]

On Tue, 2009-03-10 at 15:19 +0100, Nicholas Allen wrote:
> >
> > When you commit in a bound branch it basically does this, so I think the
> > emphasis should be on fixing that performance problem rather than adding
> > a workaround for it (and yet another workflow).
> >
> > A bound branch creates the commit locally (if it's a heavyweight
> > checkout), then pushes it to the master branch and then updates the tip
> > of the local branch.
> >
> Really? I guess I misunderstood then as I thought the commit was made on the 
> remote end first and if that succeeds then a commit is made on the local end to 
> support lock step development...

Technical the sequence is:
lock both branches
create new commit object in the local repo
push the new commit to the remote repo
update the remote branch tip
update the local branch tip
unlock

-Rob 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090311/44c88bd7/attachment-0001.pgp