Patch #4262
Bazaar: correct renames handling, other improvements
| Status: | New | Start date: | 2009-11-22 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | SCM | |||
| Target version: | - |
Description
This patch fixes some problems with Bazaar adapter, namely:
- Renames shown correctly (past behaviour was: show as modified);
- History doesn't stop on first entry rename (uses internal object ids to retrieve changes);
- Last revision the entry was changed in displayed correctly (past behaviour was: sort alphabetically, i.e. if object was changed in 2, 9, 13, then 9 would be shown);
- Field tags changed a little to make it clear to user that he can either enter local path to branch repo or
http://URL). - Bazaar adapter uses
change.revisionto store internal object ids which are pretty long, not revision number. So when viewingrepository/revisions/:id, these long ids are shown after diff link, not before it (more convenient for bazaar, doesn't change anything for other SCMs).
Patch created against r3083.
Related issues
History
#1 Updated by Ivan Korotkov over 2 years ago
- File bzr-fixes.patch added
Fixed stupid typo in patch, sorry.
#2 Updated by Ivan Korotkov over 2 years ago
- File bzr-fixes-r3235.patch added
I decided to remove internal bazaar object ids from revision view (repository/revisions/:id) at all, because they are actually never needed and tend to block the view. Taken against r3235.
Month passed since this patch was added. Seems that no-one is interested in Bazaar support for Redmine?
#3 Updated by Antti Kaijanmäki about 2 years ago
There are people interested in Bazaar support for Redmine, at least I am. ;)
I'm sure this will be merged when some developer has the time to do it.