-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per Inge Mathisen wrote:
However, you need, obviously, an sf.net account to do so. If you lack
one, contact me or gerard_ for the time being.
I'd like to have commit access on SF.net as well.
https://sourceforge.net/users/kreuvf
-BEGIN PGP
Am Mittwoch, 8. April 2009 04:42:29 schrieb bugs buggy:
I guess svn+ssh:// does something different?
It opens a ssh session and operates locally afterwards.
--DevU
signature.asc
Description: This is a digitally signed message part.
___
Warzone-dev
On Wed, Apr 8, 2009 at 4:42 AM, bugs buggy buginato...@gmail.com wrote:
Just a note, for the others that read this list, only developers need
to redownload everything...
Even developers don't need to redownload everything. svn switch works
fine even if you have svn+ssh. See my second post in
Am Dienstag, 7. April 2009 00:18:22 schrieb Per Inge Mathisen:
*) You need to check out all your working copies again. I am led to
understand that this has something to do with gna.org screwing with
the repository UUIDs. I am very sorry for the inconvenience.
Would be my fault only, not Gna's
On 4/6/09, Per Inge Mathisen per.mathi...@gmail.com wrote:
I've successfully(*) moved the svn repository to sf.net, and you can
start committing again.
However, you need, obviously, an sf.net account to do so. If you lack
one, contact me or gerard_ for the time being.
The new URL is:
I've successfully(*) moved the svn repository to sf.net, and you can
start committing again.
However, you need, obviously, an sf.net account to do so. If you lack
one, contact me or gerard_ for the time being.
The new URL is:
https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk
-
You may not need to check out your working copies again, after all. Try
svn switch --relocate --force
svn+ssh://usern...@svn.gna.org/svn/warzone/trunk
https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk
if this fails, try this first
find -name entries | xargs sed -i
