Branch specific ignores is slightly incorrect
Bug #396669 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Explorer |
Fix Released
|
Medium
|
Unassigned |
Bug Description
It feels a bit odd to set "Branch Specific/Ignores", rather than having it a working-tree property.
Certainly with lightweight checkouts it is clear that they are WT specific (since you can have 2 checkouts of the same branch, and have locally modified different ignore lists.)
However, this is mostly about how we want to display things to the user. It is possible that this is simply "Won't Fix"
Related branches
Changed in bzr-explorer: | |
milestone: | none → 0.5 |
To post a comment you must log in.
I should also mention that the way the menu is laid out, it emphasizes setting global ignores, which will *not* be versioned (and thus not propagated to other users who check out your branch).
I don't know the relative frequency of ignoring:
1) Local stuff like editor temporary files, local test files, etc.
2) Build products that stick in the tree (.pyc, .pyo) that everyone needs to ignore.
I *think* the latter is more common, which means that modifying the local ignore is more useful than modifying the global ignore.
(From SVN experience, people tend to modify their global ignores because the local ignores are not recursive. Which I've seen lead to lots of people doing "add + commit" and adding .obj, .pdb, .exe, etc files, just because they kept showing up as needing to be added.)