Edgewall Software
Modify

Opened 12 years ago

Last modified 9 years ago

#10682 new enhancement

Show the path of changesets in log view

Reported by: anonymous Owned by:
Priority: normal Milestone: next-major-releases
Component: version control/log view Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Would be great if the path of the changed file is visible in the log view. If multiple files were changed, the highest common path of all changed files should be showed.

I know this feature from WebSVN and it's very helpful to survey which parts of the project were actually changed.

Attachments (0)

Change History (6)

comment:1 by Christian Boos, 11 years ago

Resolution: worksforme
Status: newclosed

Were you really talking about the log view? I don't think so, as we show the path there.

In the changeset view, we do show the highest common path, and even in the timeline view, with the [timeline] changeset_show_files = location setting.

comment:2 by Mikael Relbe, 11 years ago

I think it would be useful to allow for an option to show the path of each individual changeset in the changeset view, similar to what is possible in the timeline view (even showing each affected file for each changeset would be *very* attractive I think).

Sorry to say, but I cannot back this up with code demonstrating this at the moment, as some of you guys would expect from me (job is killing me).

in reply to:  2 comment:3 by Christian Boos, 11 years ago

Replying to mrelbe:

I think it would be useful to allow for an option to show the path of each individual changeset in the changeset view, similar to what is possible in the timeline view (even showing each affected file for each changeset would be *very* attractive I think).

Hm, I'm afraid I don't follow you either…

Sorry to say, but I cannot back this up with code demonstrating this at the moment, as some of you guys would expect from me (job is killing me).

But some ASCII-art would be possible, I guess ;-)

For example, here's how the changeset view currently looks:

Changeset n

Timestamp: ...
   Author: ...

Location: trunk
   Files: 
          .
          tracopt/versioncontrol/git/PyGIT.py

| trunk
| - Property svn:mergeinfo changed ...

| trunk/tracopt/versioncontrol/git/PyGIT.py
| r... | r... |
|   52 |   52 | ...

So to me, it looks like we already show the full path for each change in the changeset view and, with Location:, the highest common path.

comment:4 by Mikael Relbe, 11 years ago

Oh, sorry. I meant the log view and not the changset view.

If you show the log of the root, for example, you have no clue to where each change applied. You have to click on each revision to show the change set view to find out affected paths.

in reply to:  4 comment:5 by Christian Boos, 11 years ago

Milestone: next-major-releases
Resolution: worksforme
Status: closedreopened

Replying to mrelbe:

Oh, sorry. I meant the log view and not the changset view.

If you show the log of the root, for example, you have no clue to where each change applied. You have to click on each revision to show the change set view to find out affected paths.

Ah, makes sense now. And indeed that was probably what the original reporter intended as well (I haven't looked at WebSVN in a while).

comment:6 by Ryan J Ollos, 9 years ago

Status: reopenednew

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.