question regarding bazaar

[Ville M. Vainio]

On Tue, Mar 4, 2008 at 8:27 PM, Mohit Aron <extproxy at gmail.com> wrote:

> 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.

Actually, you just brought up the thing that obviously sucks on
systems like perforce.

You are not supposed to do "bzr status" over nfs. Just branch from
nfs, then do the mods (and bzr status) there, and in the end push to
nfs.

-- 
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'