Thanks Alex, I appreciate the time taken to answer my queries!

Cheers,
- Stewart



AlexanderKitaev wrote:
> 
> Hello Stewart,
> 
>> The net change across all revisions is file.txt added, which I can derive
>> just by examining the first (added) and the last (modified).
> 
> You should also take in account that file might be copied/renamed and
> the same path may refer to the different history lines in different
> revisions. log operation of SVNKit does follow these renames from the
> newest revision in the specified range.
> 
> So you may have a history:
> 
> 1 file added
> 2 file modified
> 3 file moved to file2 (renamed)
> 
> 4 file added (this is another unrelated 'file' to the one in r1)
> 5 file changed
> 6 file2 changed
> 
> so you should call log for -rHEAD:1 for file or file2, then you'll get
> proper log entries, but, for instance just fetching a single log entry
> for file at r2 (and you will receive log entry with M file in it) will
> not mean that file you see in r6 was present in r2 (these are two
> different files).
> 
> 
> Alexander Kitaev,
> TMate Software,
> http://svnkit.com/ - Java [Sub]Versioning Library!
> http://hg4j.com/ - Java Mercurial Library!
> http://sqljet.com/ - Java SQLite Library!
> 
> 
> 
> On 26 October 2011 16:54, stewbob <[email protected]> wrote:
>>
>> Hi Alex, thanks for your answer.
>>
>> It looks like I will have to dedupe manually when I am looking at
>> multiple
>> file changes, in order to get the net change.
>>
>> For example if file.txt was added, then modified, then deleted, then
>> added,
>> then modified, the log would show me 5 entries as follows :
>>
>> 1. file.txt A (added)
>> 2. file.txt D (deleted)
>> 3. file.txt A (added again)
>> 4. file.txt.M (modified)
>>
>> The net change across all revisions is file.txt added, which I can derive
>> just by examining the first (added) and the last (modified).
>>
>> Thanks again,
>> - Stewart
>>
>>
>>
>> AlexanderKitaev wrote:
>>>
>>> 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.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Need-just-one-SVNLogEntryPath-when-logging-across-multiple-revisions-tp32718694p32724973.html
>> Sent from the SVNKit - Users mailing list archive at Nabble.com.
>>
>>
>>
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Need-just-one-SVNLogEntryPath-when-logging-across-multiple-revisions-tp32718694p32736732.html
Sent from the SVNKit - Users mailing list archive at Nabble.com.


Reply via email to