efficiency over NFS

[Nicholas Allen]

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

The only case where I could see this could be a problem is on a diskless
thin terminal where it would not be possible to branch locally from the
NFS branch and then push to it when needed. But then again if you have a
diskless thin terminal, bazaar must be running remotely too so you could
just make sure it is on the same machine as the nfs drive or branch onto
the machine where bazaar is running.

Because bazaar makes branching, pushing, pulling, merging so easy you
can always have a local working tree so I don't see this as necessary.

Nick


Mohit Aron wrote:
| Hello,
|
| I'm evaluating switching from subversion to bazaar for my company. I had
| a question that I was hoping I could get some help on.
|
| It seems one can just modify files without telling bazaar about the
| intent to do so. And then 'bzr status' has to figure out what all is
| being modified - possibly by doing a 'stat' on each file in the
| repository. While this might be ok for a local disk, this is terrible
| for workspaces on NFS. I think future bazaar releases should consider
| supporting a mode where one needs to explicitly do a 'bzr edit filename'
| to tell bazaar that it is going to modify a file (same as perforce). Any
| other files that are modified would not show up in 'bzr status' - in
| fact, it might be better if files don't have write permissions unless
| one does an 'bzr edit' on it.
|
| Please note that a 'bzr edit' doesn't need to send any message across
| the network - it just needs to be recorded in the local repository. This
| differentiates it from a similar command in version control systems like
| perforce.
|
|
| - Mohit
|

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

iD8DBQFHz7gk1+i51gqqEGkRAu4xAJ9bjBBFeDRl1r/FaAyO1BV4DVrFKQCgp2mx
s8oE2pNB+kqopcZqYDXAYME=
=cn4U
-----END PGP SIGNATURE-----