Keeping track of the Author and Committer

[John A Meinel]

James Blackwell wrote:
> 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)

Well, I have my rsync plugin with offers "bzr rpush", and Aaron's
bzrtools provides a "bzr push" (which is also an rsync). I naturally
prefer mine (I have to do more safety checks since I sync from 4-5
different locations, and didn't want to overwrite a newer revision). But
mine may not be as clean as his.

But you are correct, bzr mainline does not have a native push command
yet. (I think it is waiting for my Transport work, so that we can push
to remote branches).

John
=:->

>
>
>
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050914/dca210e5/attachment.pgp