commit --strict should consider specific includes & excludes
Bug #376304 reported by
Ian Clatworthy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
In bzr 1.14, commit --strict will abort the commit if any unknowns exist in the tree. It ought to only check for unknowns within the context of specific files (and excludes) if these are given. In other words, if the user runs
bzr commit --strict doc
and there are unknowns outside of the doc directory but none inside it, the commit ought to work. Likewise,
bzr commit --strict -x test
ought to work if the only unknowns are found in the test directory.
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: commit |
tags: | added: check-for-breezy |
To post a comment you must log in.
On Thu, 2009-05-14 at 02:27 +0000, Ian Clatworthy wrote:
>
> bzr commit --strict -x test
>
> ought to work if the only unknowns are found in the test directory.
ITYM 'not found' ;)
status triaged
importance low