Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #652 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

provide complete view of each commit

Reported by: macias Owned by: alwin
Priority: normal Milestone: not applicable
Component: All Version: 1.3.x
Severity: tweak Keywords:
Cc:

Description

When you start kdesvn and open a repo you can see a full set of files from the last commit. But for history, you can see only diffs.

On the other hand, applying diff makes a file -- so in general, creating (on-fly) a complete file is possible.

Or in other words. Let's say you have file A.txt you imported this to repo, checked out, made changes, committed, made changes, committed, made changes, committed, and so on.

For each step of commit it is possible to create a full A.txt file how it looked on this or that commit.

So, after this "introduction" my wish is to add commit timeline.

[<] commit 107(-2) [>]

which says that you are looking at the set of files which were present at point of commit 107 (which is 2 commits back from the latest state). The content of the main panes would look like today.

What's more, if user would click on any file from that commit she/he would see content of the file from that point of time, not diff.

End of the wish.

And clarification -- such feature should be additional to browsing history as diffs, not a replacement, because it says how files looked like at that time, not what was changed.

Attachments

Change History

comment:1 Changed 4 years ago by alwin

First: kdesvn let you browse trough repository on a specific revision.

Means: open repository of working copy, than Subversion -> Repository -> Select revision

Now you see the specific state. Of course you now able viewing file contents at this specific revision.

Second: In logbrowser you can select an entry on an selected revision, open the context menu and select Show this version - voila. You see the content at this history point.

I think this is what you wanted.

comment:2 follow-up: ↓ 3 Changed 4 years ago by macias

[ previously I didn't log in, sorry ]

Thank you, indeed the mechanism is there, and it is what I wished for.

The only missing parts are:

  • some GUI guidance when setting it, for example, when you select the numer of revision, there is no range show (a slider might be good). Similarly it good be set for dates (additionally to calendar way of picking up the date).
  • visual feedback after setting the release, kdesvn looks exactly the same as before. There should be some hint, what release is currently browsed

comment:3 in reply to: ↑ 2 ; follow-up: ↓ 4 Changed 4 years ago by alwin

  • Status changed from new to assigned

Replying to macias:

[ previously I didn't log in, sorry ]

Thank you, indeed the mechanism is there, and it is what I wished for.

The only missing parts are:

  • some GUI guidance when setting it, for example, when you select the numer of revision, there is no range show (a slider might be good). Similarly it good be set for dates (additionally to calendar way of picking up the date).

Hm. In selecting revisions for browsing is a date picker and some of the most known standard values of revisions like HEAD. A revision slider with max value is a little bit hard - but it is a spinbox which works mostly like a slider. (but without a maximum value).

  • visual feedback after setting the release, kdesvn looks exactly the same as before. There should be some hint, what release is currently browsed

You're right.

comment:4 in reply to: ↑ 3 Changed 4 years ago by alwin

  • Status changed from assigned to closed
  • Resolution set to fixed
  • visual feedback after setting the release, kdesvn looks exactly the same as before. There should be some hint, what release is currently browsed

You're right.

Done in commit r1898

comment:5 Changed 4 years ago by macias

Great news! Thank you.

If the slider would be possible, it would be great too -- I think it could be set from 1 to max.commit number. The calendar one is more tricky because all commits would have to be checked.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.

Ihr Browser versucht gerade eine Seite aus dem sogenannten Internet auszudrucken. Das Internet ist ein weltweites Netzwerk von Computern, das den Menschen ganz neue Möglichkeiten der Kommunikation bietet.

Da Politiker im Regelfall von neuen Dingen nichts verstehen, halten wir es für notwendig, sie davor zu schützen. Dies ist im beidseitigen Interesse, da unnötige Angstzustände bei Ihnen verhindert werden, ebenso wie es uns vor profilierungs- und machtsüchtigen Politikern schützt.

Sollten Sie der Meinung sein, dass Sie diese Internetseite dennoch sehen sollten, so können Sie jederzeit durch normalen Gebrauch eines Internetbrowsers darauf zugreifen. Dazu sind aber minimale Computerkenntnisse erforderlich. Sollten Sie diese nicht haben, vergessen Sie einfach dieses Internet und lassen uns in Ruhe.

Die Umgehung dieser Ausdrucksperre ist nach §95a UrhG verboten.

Mehr Informationen unter www.politiker-stopp.de.