Issue 622: Implement detailed commit view for Subversion

Reported by Thomas Keller, Mar 3, 2011

Continueing issue 450. Subversion and Mercurial need a proper 
implementation of SCM::getChanges() as well.

Comment 1 by Thomas Keller, Mar 3, 2011

Woops, wrong milestone

Labels: Milestone:Release1.2 ~~Milestone:Release1.1~~

Comment 2 by William Martin, Mar 3, 2011

Actually, Git backend don't cache data in a 'IDF_Commit'.

Comment 3 by Thomas Keller, Mar 3, 2011

I don't think this is needed for now if you only look at a single 
revision. You can of course cache all kind of data from the SCM in a 
local database, but this would practically mean cloning the complete 
repository into a new format (something which iirc Confluence' 
FishEye does).

Lets evaluate this and maybe other steps for IDF 2.

Comment 4 by Thomas Keller, Mar 3, 2011

Atlassian, I meant Atlassian and not Confluence, thats their wiki. 
Damn, I need sleep.

Comment 5 by Thomas Keller, Mar 18, 2011

For people familiar with either Mercurial or Subversion this would 
be a nice starter item.

Labels: Type:Enhancement GreatToStart ~~Type:Defect~~

Comment 6 by Thomas Keller, Jun 1, 2011

The detailed commit view has already been implemented for Mercurial 
in revision 09979b8551.

Summary: Implement detailed commit view for Subversion

Comment 7 by Thomas Keller, Jun 10, 2011

SVN commit details implemented in ac6be0d.

Status: Fixed
Owner: tommyd

Indefero