per-file message support into server: common config check {patch}
Bug #185224 reported by
Chad Miller
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
bzr-gtk already supports per-file commit messages. Most of its functionality should be moved into Bazaar core.
One notable reason to put these in one place is the risk of implementors getting the config key or values wrong. We shouldn't duplicate that code in several places.
Once added to the core, bzr-gtk should import this method, and on failure fall back to its current implementation. Qbzr and the built-in commit implementation can follow with implementations of per-file messages.
Changed in bzr: | |
importance: | Undecided → Wishlist |
status: | New → In Progress |
Changed in bzr: | |
status: | In Progress → Confirmed |
importance: | Wishlist → Medium |
tags: | added: commit |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
To post a comment you must log in.
I can't speak for bzr core, but I'd rather not have this functionality in QBzr. I believe it unnecessarily fractions the information that makes sense only as a whole (because is an atomic operation and applies to _all_ files), making it harder to search/display/etc. commit messages and I personally don't see any benefit.