Bazaar is ignored in some places?

Aaron Bentley aaron.bentley at utoronto.ca
Fri Dec 14 01:06:38 GMT 2007


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

Talden wrote:
>> Well, either that or the concept that each commit happens as a unit. CVS has
>> each commit separate. So you can't get (easily) a summary of what changed in a
>> given commit.
> 
> Commit atomicity provides at least two benefits...
> 
> Atomically committing a set of file modifications as a 'change'

Our data model is one of "states" rather than "changes", because states
are absolute, and easier to define completely.  So we commit a state,
not a set of changes.  Bazaar really doesn't have changesets, in this
sense.  (And neither does Subversion.)

> additionally prevents users
> pulling down incomplete changes...  Would anyone choose a tool that
> did anything else these days.

Actually, there is quite a lot of desire to pull down partial changes.
People want to be able to check out and commit to subtrees within a
larger tree.  Some codebases are so large that this is the only sensible
way to work.

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

iD8DBQFHYdce0F+nu1YWqI0RAhNlAJ9/H3z1Uje0pGBUy/7stvTWWBhDxgCfeyqr
defH7FGkhzczUASdchKeUAU=
=Omeo
-----END PGP SIGNATURE-----



More information about the bazaar mailing list