bzr: ERROR: Unknown eol value 'None'
Bug #379370 reported by
Marius Kruger
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Ian Clatworthy | ||
Bug Description
Since https:/
was fixed you are now forced to specify a eol rule whenever you define any rule.
I don't think eol rules are so special that it should insist that you define eol-rules whenever you have any rules.
Related branches
lp:~ian-clatworthy/bzr/eol-none-bug
- John A Meinel: Approve
- Diff: 56 lines
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in bzr: | |
| assignee: | nobody → Ian Clatworthy (ian-clatworthy) |
| milestone: | none → 1.16 |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Jonathan Lange (jml) wrote | #1 |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix landed in r4428.