Question/idea about multiple developers committing to one branch

[Marius Kruger]

On 12/1/06, Nicholas Allen <allen at ableton.com> wrote:
>
> ...
> bzr push mainline
> Error: The destination branch location is a shared branch and your push
> will reorder the revisions. You should use a checkout/bound branch in
> order to commit changes to this location.
> You can make this branch a bound branch by running 'bzr bind mainline'.
> You will then need to update your branch by running 'bzr update'. Then
> you can run bzr commit to commit your
> changes to this location.
>
> Then there would be no need for a --to option added to the merge
> command. This would also be something that could be implemented easily
> and would work even without smart server support on dumb file servers.
>

I think you should not force the user to bind to the branch,
he might work off-line a lot and do lots of local commits,
it will be nice to allow him this functionality
without requiring him to bind, this might be where the --to
could be usefull


regards
mairus

-- 



I code therefore I am.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20061202/cd38f17b/attachment.htm