I have a few questions about Git implementation. Currently we've done it with two limtations:
Firstly, it works only if in a commit only one file was renamed. Git doesn't handle renames separately - this is just file deletion and file creation. So now when you go to file history it tries to find commit where file with current name was created and some other file deleted - then it is probably rename. To fix one-file-in-commit issue, we have to compare contents of the files and diffs and this can be time consuming. Do we have to or current implementation will be enough? Secondly, it doesn't show renames for folders (it works for files in the folder though). This seems to be possible to implement but logic will be very tricky. Do you need to show renames of folders? --- ** [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:** Tue Jul 23, 2013 08:25 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): http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/turbojpeg.c?view=log This is a critical feature for being able to visualize the history of a repository. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
