On Thu, Mar 6, 2014 at 5:44 PM, jrm wrote:
> Working on some tools for a development environment that will make use of
> SVN. There are circumstances where I want to create temporary information
> of my own, related to checked out versions. Rather than cluttering up the
> working directory with
Working on some tools for a development environment that will make use
of SVN. There are circumstances where I want to create temporary
information of my own, related to checked out versions. Rather than
cluttering up the working directory with other special directories and
files, I was wonde
We have a problem with the new 1.8 subversion clients (we use
TortoiseSVN 1.8.5 and SlikSVN 1.8.5). It seems that the new SVN 1.8
feature of being able to keep using your feature branch after
reintegration is not working in some cases.
It is not working when the trunk contains local mergeinfo
HI Bert,
thank you four your quick response. comments inlined:
From: Bert Huijben [mailto:b...@qqmail.nl]
Sent: jeudi, 6. mars 2014 14:30
To: Hagen Hentschel (Ellisys); users@subversion.apache.org
Subject: RE: resolution of relative external path for given 'peg
The relevant change was in revision r1428637
[[
r1428637 | julianfoad | 2013-01-03 23:13:26 +0100 (do, 03 jan 2013) | 7
lines
Maintain vertical alignment of 'svn status' output with up to 8-digit
revision numbers be
At which URL do you set the ‘svn:externals’ property?
And on which URL does the node have when you perform the update?
The ../../ is applied against the URL the node has at the time of running
update/checkout. If that node has a different url then when you tagged it (and
that is a problem
Hi,
I am not in the list, so please Cc me for any feedback.
I have the following use case that does not work and I think it's a
(conceptual) bug with 'pegged' AND 'relative' externals:
- consider the following structure (revision 1)
/proj/lib/a/trunk/
/proj/app/b/trunk/
- now we add a 'p
