Hi,
-Original Message-
From: Leonardo Azize Martins [mailto:laz...@gmail.com]
Sent: Friday, June 11, 2010 2:16 PM
To: Bob Archer
Cc: users@subversion.apache.org
Subject: Re: svn move directory will create a new revision for every file
inside
this directory?
Hi Bob,
You have
On Thu, Jun 17, 2010 at 05:38, emerson echofloripa.y...@gmail.com wrote:
Hi Guys
Thanks for the answers.
First Andy, yes, we put more than the story code on the commits :)
We are using svn 1.4.4 ont he server, so to be able to keep track of
the ancestors logs we will probably need to
Hello,
From: nsnc_eee nsnc_eee [mailto:nsnc...@yahoo.co.in]
Sent: 17 June 2010 14:07
Subject: VSS TO SVN Migration Info
Hi,
This is Sabrinath, i am working as a Build And Release
Engineer. I recently joined in other Company where they are
using VSS as Source Code repository
Another option is to establish a single SSH session using port mapping
and then run all of your SVN traffic across that.
Something like
ssh -L 3690:svn_server:3690 ssh_server
svn svn://localhost/
The first line says take any traffic destined for the svn port on my
machine and send it to
That is a very good question.
Our subversion server has not been updated in a while and it is still on
version 1.4.2. I was looking into updating it to take advantage of the
new merge tracking features (among others).
Since we are using such an old version, I wanted to replicate our
production
On Jun 17, 2010, at 15:09, Alin wrote:
Note that Subversion 1.4.x and earlier are unsupported by now, and when
1.7.0 comes out, support for 1.5.x will be dropped. Why do you need to use
such an old version?
That is a very good question.
Our subversion server has not been updated in a
No problem. That was a good tip from Ryan on the start-commit hook. I wish I
had know about it, although we did publicize to our users well in advance that
they needed to upgrade and they could do it anytime before we did our server
upgrade. I really only got one call from a user and he was
On 6/17/2010 3:09 PM, Alin wrote:
That is a very good question.
Our subversion server has not been updated in a while and it is still on
version 1.4.2. I was looking into updating it to take advantage of the
new merge tracking features (among others).
Since we are using such an old version, I
