By the way, it seems that there's a bug in ForgeSVN (or pysvn).
How to reproduce
- create a file, commit it
- rename it using svn move {src} {dest}, commit
- go to revision where file was created and open it's history
- there should be at least one commit (about creation) but there are none of
them
I've spent little time debugging it and noticed that exception is thrown
`File not found: revision 3, path '/dir/a.txt'`, even if file was created in
revision 2 and revision_start=revision_2
---
** [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:** Thu Aug 08, 2013 11:38 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.
