Keyword Expansion
Bug #408841 reported by
Nick Trew
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Undecided
|
Ian Clatworthy | ||
Bazaar Keywords Plugin |
Fix Committed
|
High
|
Ian Clatworthy |
Bug Description
Bzr-keywords doesn't seem to expand or collapse keyword placeholders, despite having rules in ~/.bazaar/rules.
After some discussion on IRC, I can confirm that keywords are expanded when branching a repository, but I believe there are some issues with checkouts (the format not supporting keywords, or something similar).
I think ideally keywords should be expanded/updated upon commit, so they can be seen locally as well as from any branches.
Related branches
lp:~ian-clatworthy/bzr/finish_commit_hook_2
- Robert Collins (community): Approve
- Diff: None lines
Changed in bzr-keywords: | |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in bzr: | |
status: | New → Fix Released |
assignee: | nobody → Ian Clatworthy (ian-clatworthy) |
milestone: | none → 2.0.0rc2 |
To post a comment you must log in.
A fix for 385879 has been proposed for merging into 2.0. So that's part of the problem addressed.
The other issue is whether the core commit code or the keywords plugin should be responsible for refreshing the keywords in working tree files post commit. My initial reaction is to be make it the responsibility of this plugin via registering a post-commit hook. I'll try that now.