bzr: ERROR: Unknown eol value 'None'

Bug #379370 reported by Marius Kruger on 2009-05-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ian Clatworthy

Bug Description

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

Martin Pool (mbp) on 2009-05-25
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
Jonathan Lange (jml) wrote :

Fix landed in r4428.

Changed in bzr:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers