Bazaar File System

Registered by Wim on 2009-11-03

I am running bazaar with a big project (>36000 versioned files). This makes commands like "bzr status" and "bzr commit" quite slow. It would be nice if bazaar supplied a "bazaar file system" mountable with fuse (I'm using ubuntu) that simply keeps track of changes while they happen. This way the tool would not need to recompute the status all the time. In addition it would allow for nice features such as "cd .revision-14" to see that the state was in revision 14.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

I think bzrfs should really be an additional feature, not a choice you have to make up-front. As such you would still have your local checkout in a normal directory. The bzrfs would map the file system to the same directory, but adds automatic tracking of changes, such that commit does not have to search for them. If bzrfs terminates (intentionally or unintentionally) you still have your checkout available.

It would be nice to have the same capability without a bzrfs. For huge trees bzr commit takes too much time and so you want to tell bzr which files you change when you change them (eg: bzr edit file.py)

As for "bzr status", I think only a bzrfs can prevent the time consuming tree traversal.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.