Question/idea about multiple developers committing to one branch

[Aaron Bentley]

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

Jan Hudec wrote:
> On Wed, Nov 29, 2006 at 08:56:19AM -0500, Aaron Bentley wrote:
>> Nicholas Allen wrote:
>>> What I think would be cool is if the smart server could enforce that all
>>> commits coming into it are through bound branches or checkouts.
>> I can see why that has some merit.  There's no way of knowing whether a
>> commit is coming from a checkout or not, though.
>>
>> I think it would be simpler to enforce just the rule that no one can
>> change the revision ordering.
> 
> ... and have the advantage that than merge could have an argument
> (--to), that would cause the parents to be recorded in reverse order, so
> than the developer would just 'bzr merge --to mainline; bzr commit; bzr
> push mainline' This would change their local revnos(*), but would properly
> reflect the project structure in log structure (and revnos on the
> mainline).

The way update operates?  Sure, makes sense.

Aaron

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFcFyD0F+nu1YWqI0RAgZ7AJ9l0LKWe5NvDBklk1ciFgUNjWFefQCdFxAR
5Rc55zGP4DfB+N5xTojmf/g=
=Zi2K
-----END PGP SIGNATURE-----