hi..
I am getting always an error while installing project from google repositry
..
Open SVN Repository perspective
- Right click on the left side and go to new -> repository location...
- URL: https://quantdesk.googlecode.com/svn/trunk
- Press Finish
- Open the repository, right click on QuantD
Thank you Mark for your immediate response.
1) Did we require to write any scripts or we can directly we can migrateusing
the tool?
2) We are going to migrate JAVA code will there be any issues?
Regards,
Sabarinath.
--- On Thu, 17/6/10, Cooke, Mark wrote:
From: Cooke, Mark
Subject: RE: VS
> One good way to copy the repository would be to "svnadmin dump" on
> the production server and "svnadmin load" on the test server. This
> would automatically upgrade the repository to the latest most
> efficient format.
Don't forget this dump/load process will not copy hook scripts and
locked
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 w
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 a
Ryan and Thomas,
Thank you very much for your advice.
-Original Message-
From: Ryan Schmidt
To: Thomas Loy
Cc: Tomoiaga, Alin , users@subversion.apache.org
Subject: Re: older versions of the subversion server
Date: Thu, 17 Jun 2010 15:24:56 -0500
On Jun 17, 2010, at 15:18, Thomas Lo
On Jun 15, 2010, at 12:20 PM, Eiren Smith wrote:
On Jun 15, 2010, at 12:14 PM, Stefan Sperling wrote:
On Tue, Jun 15, 2010 at 11:49:44AM -0400, Eiren Smith wrote:
Sir:
Thanks for your reply. I'll read those references you cited.
P.S. Other files may also be missing from the revprops/ dir,
On Jun 17, 2010, at 15:18, Thomas Loy wrote:
> On the bright side, we had virtually no issues on our upgrade – the major
> issue was trying to get all of our users to upgrade their clients.
There is at least a way you can automate advising your users to upgrade to
Subverison 1.5 or later if th
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 upda
We just upgraded from 1.3 to 1.6.x. Fortunately, we also got new servers for
the new version, so that helped up. We upgraded by installing SVN on the new
servers, exporting our repositories from the old (current production) servers,
and importing to the new servers. If you have that option, i
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 e
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 the
Please use < Reply ALL > to keep messages on list (and try not to
top-post)...
> From: Cooke, Mark
> Subject: RE: VSS TO SVN Migration Info
> To: users@subversion.apache.org
> Cc: "nsnc_eee nsnc_eee"
> Date: Thursday, 17 June, 2010, 7:39 PM
>
> Hello,
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 repo
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 and
i'm new to this. In my prev company we used SVN and i am satisfied with the SVN
and its Features. I am planing to Migrate the Source
On Thu, Jun 17, 2010 at 05:38, emerson 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 upgrade.
Note that the 1.4
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 upgrade.
Still, I believe we need some tool to search the logs for that
especific #xx
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,
>
18 matches
Mail list logo
