Skip Menu |

This queue is for tickets about the SVN-Web CPAN distribution.

Report information
The Basics
Id: 21451
Status: stalled
Priority: 0/
Queue: SVN-Web

People
Owner: Nobody in particular
Requestors: matthew [...] veradox.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: diff arbitrary revisions of a subtree
I'm envisioning output just like SVN::Web::Revision, where it lists all the subdirectories and files added/deleted/changed between the two revisions, and then html diffs of the ones that changed. You could choose which revisions to diff from the "browse" screen of a subtree: two textboxes where you type in the two revision numbers, with the minimum being the revision the directory appeared, and the maximum being the most recent revision.
Subject: Re: [rt.cpan.org #21451] diff arbitrary revisions of a subtree
Date: Tue, 12 Sep 2006 19:38:03 +0100
To: bug-SVN-Web [...] rt.cpan.org
From: Nik Clayton <nik [...] ngo.org.uk>
Matthew Wilson via RT wrote: Show quoted text
> Tue Sep 12 13:07:52 2006: Request 21451 was acted upon. > Transaction: Ticket created by WILSON > Queue: SVN-Web > Subject: diff arbitrary revisions of a subtree > Broken in: (no value) > Severity: Wishlist > Owner: Nobody > Requestors: matthew@veradox.com > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=21451 > > > I'm envisioning output just like SVN::Web::Revision,
This needs to be a bit more specific. Consider the current Revision action output:, which broadly looks like this: For example, suppose I have a file, trunk/foo, which was changed in r1, r2, and r3. Are you expecting the layout to be: [ metadata for r1 ] [ log message for r1 ] [ list of files ] [ diff for r1 ] [ metadata for r2 ] [ log message for r2 ] [ list of files ] [ diff for r2 ] [ metadata for r3 ] [ log message for r3 ] [ list of files ] [ diff for r3 ] Or: [metadata for r1 ] [log message for r1 ] [ list of files ] [ metadata for r2 ] [ log message for r2 ] [ list of files ] [ metadata for r3 ] [ log message for r3 ] [ list of files ] [ diff from r1 to r3 ] Or something else? N
This one: For diff purposes, treat the whole set of revisions as if it's just 1 revision. [ don't display info for r1 since it's the baseline of the diff ] [ metadata for r2 ] (I personally would not include [ metadata for r3 ] this metadata in my templates) [ log message for r2 ] [ log message for r3 ] [ list of files ] (add/delete takes precedence over modify) [ diff from r1 to r3 ] (Only list and diff the files that still exist in r3 and already existed in r1. Don't diff files added or deleted in the interim.)
I doubt youre still interested in this. I will leave this as stalled in case anyone wants to submit a patch.