Opened 20 years ago
Closed 19 years ago
#1014 closed enhancement (duplicate)
Diff between arbitrary revisions in the File module
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control/changeset view | Version: | 0.8 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
It would be nice to be able to get a diff between two arbitrary revisions for a given file in the sourcecode module. Currently, sourcecode module only allows to see the diff between two successive revisions, but sometimes it's nice to be able to do so between two arbitrary revisions.
I've been told that it would be time consuming on the server, but for some usage, for example, internal use in a company, security problems like DoS are not an issue.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
Summary: | Diff between arbitrary revisions in the sourcecode module → Diff between arbitrary revisions in the File module |
---|
comment:2 by , 20 years ago
What I mean by currently one can already see the diff of two successive revs is that the Changeset module allows to see :
- all the changes of the changeset
- the changes of the changeset on a particular file (which is in fact the diff of a file between two successive revisions)
comment:3 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I think I misunderstood the original reporter's request due to his usage of the term sourcecode module.
I believe what he wanted was simply #199, so this should have been closed as a duplicate in the first place.
On the other hand, what I suggested in my previous comment has been implemented in the TracDiff branch: from the browser module, there's now a direct access to the diff with between the current and the previous revision of the current node, by the way of a Last Changes link.
This link goes to what I call the restricted changeset view, i.e. a subset of a given changeset where only the changes on the paths related to that given node are shown.
From there, a Previous diff link goes to the restricted changeset view for the previous changeset in the node's history.
This makes it easy to go through the change history of a path of interest (a file or a directory).
comment:4 by , 19 years ago
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Type: | defect → enhancement |
from the browser module, there's now a direct access to the diff with between the current and the previous revision of the current node, by the way of a Last Changes link.
Will be Last Change
From there, a Previous diff link goes to the restricted changeset view for the previous changeset in the node's history.
Will be Previous Change
Now resolving this ticket as a duplicate of #199.
This is a long standing issue…
There are multiple things that could be done on the topic of diffs:
As we already have a ticket for the first way (#199), I think this ticket should be devoted to the second way.
To that effect, I think a little bit of clarification is needed in the summary. What is called sourcecode module by thomas is the File module, I guess. I'm not sure to what he refers when he says that currently one can already see the diff of two successive revs. That's the Changeset module, which is quite a different beast, and more amenable to something like #199.