#1160 closed enhancement (fixed)
Specify Revision Log RSS target URL
Reported by: | xamen | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 0.10 |
Component: | version control/log view | Version: | 0.8 |
Severity: | normal | Keywords: | log rss restricted changeset |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I would like to be able to specify what the RSS target URL should point to, for example:
Currently: http://projects.edgewall.com/trac/browser/?rev=1140
I would like to be able to specify going directly to the Changeset instead: http://projects.edgewall.com/trac/changeset/1140
So that when I view the RSS feed, I can see exactly which files have changed.
Attachments (0)
Change History (5)
comment:1 by , 20 years ago
comment:2 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Well, the Changeset View is now ([1864]) the targeted URL for each changeset item in the Revision Log feed.
I think that's a reasonable default for now.
With the TracDiff features, however, it would be possible to link to the restricted changeset view, i.e. the changes that happened below the path on which the Revision Log feed was created.
comment:3 by , 19 years ago
Keywords: | restricted added |
---|---|
Milestone: | → 1.0 |
comment:4 by , 19 years ago
As TracDiff is now in trunk, it would be now possible to implement the above suggestion, but I'm not sure if that's such a good idea.
Better to link to the full changeset, no?
comment:5 by , 19 years ago
Milestone: | 1.0 → 0.10 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Well, as it's easily possible to go from the restricted changeset to the full changeset, it's maybe better to show the restricted changeset.
That way, the navigation (Previous Change/Next Change) stays on the path from which the RSS feed was subscribed.
Fixed in r2821.
Well, I'm not sure this is the best way, but I've changed the file Log.py on line 75 from this:
to this: