I think downgrading it to a warning would be ok. I've noticed other
systems do the same thing.

That said, if you are upgrading 400 machines to a newer version of bzr,
can't that same mechanism be used to call 'bzr whoami' one time on each
of those machines? (It doesn't have to happen on every commit, just one
global setup.) Certainly you're running 'bzr commit' on all of those
machines as well (or you wouldn't have had the problem in the first
place)....

I can agree that change is disruptive, but having appropriate defaults
for the common case is also useful.


** Changed in: bzr
   Importance: Undecided => Medium

** Changed in: bzr
       Status: New => Confirmed

-- 
bzr commit error because of no identity
https://bugs.launchpad.net/bugs/616878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to