Opened 17 years ago
Last modified 10 years ago
#6599 new enhancement
redirect in trac browser after file got moved in svn
Reported by: | ThurnerRupert | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | version control | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
it would be nice if trac would make a redirect after a file got moved in svn. in this case the "source:" links stay valid and could be adjusted afterwards.
a second possibility would be to have a function which adjusts the source wiki links to the new location.
Attachments (0)
Change History (5)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
If you want to keep valid links specify the revision along with the path, such as in [source:/trunk/COPYING@200]. See TracLinks.
How would Trac deal when a file is moved, then another file is created with the very same name? The link would be "valid" but points to a different file.
Moreover, as SVN does not really track file move (only copy and deletion), it would probably quite difficult to provide a "safe" implementation. Image a use case where a file is duplicated into two copies and the source deleted within the same changeset. What would be the new "destination" file for this kind of automagic links?
comment:3 by , 17 years ago
trac currently already displays the link to the old destination in the history browser. replacing the old link in the wiki pages / ticket texts with the new one could be a possible solution, which also copes with (i think very rare case of) having a new file on the location of the old one.
specifying the revision is not the solution, as the link should point to the newest version.
for the search: what do you have installed to have this link? i can see it on teo, but not in our 0.10.4 rep?
comment:4 by , 14 years ago
Milestone: | next-major-0.1X → unscheduled |
---|
comment:5 by , 10 years ago
Owner: | removed |
---|
Did you notice the "search" link you'd find in such pages?
e.g. source:sandbox/pycon/ninja
This is however a somewhat costly operation to do, that's why we don't do this automatically.
The second possibility is, well, more a Trac 3.0 sort of thing …