news_merge should be configurable, in-tree
Bug #529213 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Many projects have a NEWS-like file, but slightly different heuristics
will be needed. E.g. they use ~~~~ not #####, or ----- not *****.
It would be great if we could set the appropriate info
in .bzrmeta/news_merge [perhaps .conf], so that a tree with slightly
different needs can be customised. I'd also like to be able to set the
filename for news_merge there.
affects bzr
status confirmed
done
I don't know what the importance is. Arguably this is 'make merge great'
so part of the current focus, otoh maybe its not.
-Rob
tags: | added: check-for-breezy |
To post a comment you must log in.
I'm tempted to think this does fit with "make merge great". Not so much because a custom merger for NEWS is great (although it is nice), but because building the infrastructure to make it easy for people to build good (configurable, powerful, reasonably efficient, etc) custom mergers would be great.