Hi,
I'm accessing a SVN repository from Java code using javahl. Now, I'd
like to analyze the diff of the svn:mergeinfo property (what other
revisions were merged into some branch in a commit). The only way I
found doing that is using the API
{{{
On 06.05.2015 08:24, Bernhard Haumacher wrote:
Hi,
I'm accessing a SVN repository from Java code using javahl. Now, I'd
like to analyze the diff of the svn:mergeinfo property (what other
revisions were merged into some branch in a commit). The only way I
found doing that is using the API
-Original Message-
From: Branko Čibej [mailto:br...@wandisco.com]
Sent: woensdag 6 mei 2015 14:49
To: users@subversion.apache.org
Subject: Re: API accessing property diff of svn:mergeinfo
On 06.05.2015 14:20, Bernhard Haumacher wrote:
Hi Branko,
On 06.05.2015 08:24,
On Wed, May 6, 2015 at 8:20 AM, Bernhard Haumacher h...@haumacher.de
wrote:
Hi Branko,
On 06.05.2015 08:24, Bernhard Haumacher wrote:
... I'd
like to analyze the diff of the svn:mergeinfo property (what other
revisions were merged into some branch in a commit). ...
On 06.05.2015 14:20, Bernhard Haumacher wrote:
Hi Branko,
On 06.05.2015 08:24, Bernhard Haumacher wrote:
... I'd
like to analyze the diff of the svn:mergeinfo property (what other
revisions were merged into some branch in a commit). ...
ISVNClient.getMergeinfoLog should give you
Hi,
I have a question,,,
I Installed Subversion for Windows on a VM and set up a project using
TortoiseSVN
We need to access the SVN from remote offices vis https
What is the process to set up the remote access allowing users to access the
project?
Thanks
Stan
On Wed, May 6, 2015 at 8:07 PM, Scott Aron Bloom sc...@towel42.com wrote:
So I noticed something..
We use svn:externals quite a bit, using the format
-r 1234 ^/externals/ lcldr
And it works just fine, we never moved to the “new” format of
^/externals/@1234
However,
So I noticed something..
We use svn:externals quite a bit, using the format
-r 1234 ^/externals/ lcldr
And it works just fine, we never moved to the new format of
^/externals/@1234
However, recently, we found that in restructuring one of our externals
directory, which caused to