As an addendum this command is being executed through tsvncmd.

tsvncmd:command:diff?path:SVN+https://someurl?path2:\\somefolderonserver
On Monday, May 22, 2023 at 4:17:25 PM UTC+12 Alfred E. Neuman wrote:

> Our SVN command line tool is Apache SVN. Are you doing the diff command 
> and supplying a URL for path1 and a path for path2? It consistently 
> converts any forward slashes to back slashes for me.
>
> On Saturday, May 6, 2023 at 3:44:24 AM UTC+12 lorenznl wrote:
>
> Alfred E. Neuman via TortoiseSVN wrote: 
> >You will need the Pro Edition but it is achieved by adding a prefix of 
> SVN+ 
> >to the URL of the subversion repository you're comparing against. 
>
> I tried that and, lo and behold, it work for me. 
>
> What subversion commandline client do have installed? 
> I'm using TortoiseSVN and the commandline client that comes with it 
> -- 
>
> Lorenz 
>
> > 
> >e.g. https://anotherserver.com/subversion/somefolder 
> >Becomes 
> >svn+https://anotherserver.com/subversion/somefolder N 
> >On Thursday, May 4, 2023 at 6:56:01?PM UTC+12 lorenznl wrote: 
> > 
> >> I've used BeyondCompare only for comparing lokal files via the 
> >> explorer context menu integration. 
> >> 
> >> How do I compare a (lokal) file with a file in a subversion repository 
> >> using BeyondCompare? 
> >> -- 
> >> 
> >> Lorenz 
> >> 
> >> 
> >> Alfred E. Neuman via TortoiseSVN wrote: 
> >> 
> >> >You are correct. The file is reachable via Windows explorer on an 
> >> internal 
> >> >server but it is not under version control. The file I am comparing it 
> >> >against is in a web-based subversion repository. 
> >> > 
> >> >The diff tool I am using is Beyond Compare 4 and it is compatible with 
> >> >viewing subversion repositories. I am not sure whether the URL being 
> >> >converted to a path is from TortoiseSVN or Beyond Compare 4 (but I 
> don't 
> >> >think it'd be the latter given it offers subversion comparison). 
> >> > 
> >> >As another example, if I compare: 
> >> >\\someserver\somefolder\somefile.png 
> >> >With 
> >> >https://anotherserver.com/subversion/somefolder/somefile.png 
> >> > 
> >> >The url is processed as 
> >> >https:\\anotherserver.com\subversion\somefolder\somefile.png 
> >> >And so a comparison cannot take place with a local file against the 
> >> >subversion repository (now interpreted as a folder path) 
> >> >On Wednesday, May 3, 2023 at 3:21:11?AM UTC+12 lorenznl wrote: 
> >> > 
> >> >> Alfred E. Neuman via TortoiseSVN wrote: 
> >> >> 
> >> >> >I have a remote server which outputs test results which I would 
> then 
> >> like 
> >> >> >to compare against expected results in my remote SVN repository. 
> The 
> >> >> remote 
> >> >> >server is accessible via file explorer but the remote SVN 
> repository 
> >> is 
> >> >> >not. When attempting to use the diff command, the URL I supply for 
> the 
> >> >> >remote SVN repository has all \s replaced with /s this making it 
> >> >> >inaccessible for my diff tool. 
> >> >> >[...] 
> >> >> 
> >> >> can you explain in more detail what you are doing? 
> >> >> 
> >> >> So far I understand, that you have a file (reachable via windows 
> >> >> explorer on a file share). 
> >> >> I assume this file is not under version control? 
> >> >> 
> >> >> The file to which to compare is versioned and accessible via 
> >> >> Repository URL. 
> >> >> 
> >> >> What diff-tool are you using? 
> >> >> It sounds like it's not TortoiseUDiff. 
> >> >> 
> >> >> To directly diff a file in the file system against a file in a 
> >> >> subversion repository, the diff-tool would need to connect with the 
> >> >> subversion server to abtain a copy of the file in the repository. 
> >> >> Not all diff-tools support that. 
> >> >> -- 
> >> >> 
> >> >> Lorenz 
> >> >> 
> >> >> 
> >> 
> >> 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/261655d3-2d55-44d7-8aaa-2733abdccf7fn%40googlegroups.com.

Reply via email to