efficiency over NFS

[Aaron Bentley]

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

Mohit Aron wrote:

>     Sure. Take the example of a typical company that has a centralized
>     repository and many developers using that. The developers may choose
>     either the centralized workflow, or the decentralized workflow with
>     a shared mainline (as explained in http://bazaar-vcs.org/Workflows).
> 
>     Now the issue is that a developer can't be expected to do a commit
>     and push to the centralized repository after every line of code that
>     is written by him/her.

No, but that is why checkouts and lightweight checkouts exist.  At my
old company, every developer had their repository on a central,
backed-up NFS server, and a lightweight checkout on local disk.  That
way, every commit they made was backed up, but they didn't have to use
NFS for their workspace.

The "bzr edit" command you're suggesting is something we've pondered
since we started the project, but so far, we've never found a compelling
reason to implement it.

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

iD8DBQFHz6ky0F+nu1YWqI0RAiXEAJ96h6iNvhP/9o03DM1MP4xuGPoQEwCfSdAW
DA7qfgFtRHBVUKfGoZQHS1o=
=Vkbh
-----END PGP SIGNATURE-----