Recent changes to feature-requests

#26 Support SVN repo paths more directly

michael-m — Tue, 16 Jun 2020 17:32:21 -0000

status: accepted --> closed

#26 Support SVN repo paths more directly

michael-m — Fri, 29 May 2020 01:35:41 -0000

status: unread --> accepted
assigned_to: michael-m
Group: Proposed --> Next Release

#26 Support SVN repo paths more directly

DorothyR — Mon, 30 Sep 2019 20:49:04 -0000

I have just checked in a fix for this. It was vexing me, too.

Support SVN repo paths more directly

Matthew Gavin — Wed, 11 Sep 2019 17:42:27 -0000

I am using tkdiff 4.3.5 with SVN on Red Hat 7 linux.

It seems that the following works as expected:

linux%> tkdiff -r<r1> -r<r2> <path_to_file)in_working_copy> // works nicely</path_to_file)in_working_copy></r2></r1>

However, the following does NOT work as expected. It is similar to the above, except it uses an SVN repo file server path, not a path to a file on the local drive, for the base file location. For the following example, tkdiff is unable to find the SVN file revs on the SVN server (r1 and r2) and instead uses the HEAD revision (not r1 and r2) for both files in the compare, which is not what we are asking for. As a result the answer is always "files are identical" for a compare of HEAD vs HEAD.

  linux%> tkdiff -r<r1> -r<r2> <http://svn_repo/path/to/file/on/server>      // not supported by tkdiff ?

The workaround (which works) is to specify the full SVN server path and use the "@<rev>" syntax, to specify both files/revs in the compare, but this takes more effort:</rev>

    linux%>tkdiff <http://svn_repo/path/to/file/on/server>@r1 <http://svn_repo/path/to/file/on/server>@r2              // works OK, but a bit clumsier than the above

So tkdiff does (somewhat clumsily) support this case, but it wasn't what I expected ater years of using "tkdiff -r<r1> -r<r2> <file>" for files local to my drive.</file></r2></r1>

I would also note that this proposal would more closely align tkdiff with svn diff, as svn diff does support the proposed syntax:

linux%> svn diff -r<r1> -r<r2> <http://svn_repo/path/to/file/on/server>      //  supported  by SVN diff

I would suspect this would be a relatively simple chage to make to the tkdiff parser.

Thanks -

Matt Gavin

Support SVN repo paths more directly

Matthew Gavin — Wed, 11 Sep 2019 17:42:27 -0000

Ticket 26 has been modified: Support SVN repo paths more directly
Edited By: michael-m (vampm)
Status updated: u'unread' => u'accepted'
_milestone updated: u'Proposed' => u'Next Release'
Owner updated: None => u'vampm'

Support SVN repo paths more directly

Matthew Gavin — Wed, 11 Sep 2019 17:42:27 -0000

Ticket 26 has been modified: Support SVN repo paths more directly
Edited By: michael-m (vampm)
Status updated: u'accepted' => u'closed'

#24 Display timestamp of each file

michael-m — Thu, 09 Aug 2018 02:55:26 -0000

status: pending --> closed

#24 Display timestamp of each file

michael-m — Sat, 04 Aug 2018 19:11:28 -0000

status: open --> pending
assigned_to: michael-m
Group: --> Next Release

#1 feature improvement to tkdiff

michael-m — Thu, 07 Jun 2018 15:53:43 -0000

labels: --> FAQ
status: open --> closed
assigned_to: michael-m
Group: --> Next Release (example)

#23 Report in format similar to -U of diff

michael-m — Thu, 07 Jun 2018 15:30:00 -0000

status: open --> wont-fix
assigned_to: michael-m
Group: --> Next Release (example)