incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DRC" <>
Subject [allura:tickets] #5775 Allura Code Viewer: provide "copied from" link in history view
Date Mon, 05 Aug 2013 11:16:33 GMT
>From my point of view, I am simply trying to get back the SVN browsing functionality that
ViewVC had, so the details of the git implementation aren't currently important to me personally,
although others may have their own opinions on that.  I would say that the same principle
applies-- provide the same functionality that your old git viewer provided.

The basic workflow I need is:
-- pull up the history view of a file or folder
-- if at some point in the history, the file/folder was renamed or moved, then I want a link
to a history view of the previous incarnation of the file/folder, so I can keep tracing the
history back.

Currently, there is no way of distinguishing from the first revision of a file/folder and
the first revision after it was copied/moved/renamed.  Even if you know that it was copied/moved/renamed,
it's difficult to figure out what the old name was, and even if you know the old name, you
have to go through the trouble of setting a sticky revision in the browser in order to even
find the old version in the tree.


** [tickets:#5775] Allura Code Viewer: provide "copied from" link in history view**

**Status:** in-progress
**Labels:** 42cc 
**Created:** Thu Feb 07, 2013 09:12 PM UTC by DRC
**Last Updated:** Mon Aug 05, 2013 10:55 AM UTC
**Owner:** nobody

This is one of several tickets I am creating to log what I feel are shortcomings in the new
(Allura) code viewer relative to the old (ViewVC) code viewer. In all of these cases, simply
providing a way for users to continue using ViewVC would be an acceptable workaround.

In ViewVC, if a file or directory had been renamed, then the history view of said file/directory
provided a link at the bottom that allowed one to easily browse the old history of the file/directory
before it has been renamed.  Example (see bottom of page):

This is a critical feature for being able to visualize the history of a repository.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message