Hello, SVNLogEntry always corresponds to a single revision. So you always will get as much log entries as there are revisions.
In general, Subversion tracks versions of the file tree as a series of changes that converts one tree to another and such a description is a "revision" you receive in a form of SVNLogEntry. For instance, in rN you may have: /trunk/file.txt /trunk/file2.txt Then file.txt is modified and file3.txt is added, so tree from rN+1 is: /trunk/file.txt /trunk/file2.txt /trunk/file3.txt And rN+1 is described (always relatively to the previous revision) as: M /trunk/file.txt A /trunk/file3.txt When you specify a paths for a log operation, then SVNKit (and Subversion) merely filters log output to include only those revisions (differences) that include paths being specified, but files themselves are not versioned individually and revision always describes a changes of the whole repository. Alexander Kitaev, TMate Software, http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 25 October 2011 18:59, stewbob <[email protected]> wrote: > > Hi, > > I'm using SVNRepository.log() to look at changes across multiple revisions. > > Any changed paths are grouped by SVNLogEntry (single revision). So if a > single file was added in one revision, then changed in another, if the log > runs across both revisions, I will get two SVNLogEntry objects. > > I would like a way of just getting one SVNLogEntry for each file across > multiple revisions, even if lots of changes have occurred. So a true delta > across all the revisions. > > Is there an easy way to do this? > > I could dedupe myself but I wondered if SVNKit had a feature that could > help. > > Thanks, > - Stewart > -- > View this message in context: > http://old.nabble.com/One-SVNLogEntryPath-shown-when-logging-across-multiple-revisions-tp32718694p32718694.html > Sent from the SVNKit - Users mailing list archive at Nabble.com. > > >
