Keeping track of the Author and Committer

[James Blackwell]

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi *,
> 
> as it is possible to mutliple people to bzr push to a tree,


I'm sorry Stefan, but as far as I know there's no push support built into
baz-ng yet. 

In the meantime, I believe most people publish their branches by
performing an rsync (you can think of it as a cp -r)


> I think it would be very usefull, to seperate the author of a changeset
> and the committer, as GIT does it, so if someone merge someoneelse's
> changes to a a tree, the committer should allways be the person who
> actually move the change set to the target branch, and the author should
> be the person who, wrote the code and does a bzr commit to his local
> branch. so if a changeset is moved visists more than one branch until it
> reaches the master branch, the author is still the same in all branches,
> but the committer is (maybe different in each branch) and represents
> allways the committer to the specific branch...

> 
> Comments?
> 
> - --
> metze
> 
> Stefan Metzmacher <metze at samba.org> www.samba.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3-nr1 (Windows XP)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFDJn9wm70gjA5TCD8RAnoTAJ9hXAtdt7dVtilPeNM761T9HbOfbwCgsWHe
> UBvB+m/rHdv56afI4BkVa/I=
> =ZfVq
> -----END PGP SIGNATURE-----

-- 
 James Blackwell      |   Try out the blog planet for revision control
 Tell someone a joke! |   at http://planet.revisioncontrol.net
----------------------------------------------------------------------
GnuPG (ID 06357400) AAE4 8C76 58DA 5902 761D  247A 8A55 DA73 0635 7400