Hey everyone,
please be cautious!!!
it seems that svn keeps your password and it asks you for the password
only once (the first time you do a commit), so make sure you don't give
access to your amsn directory..
Alvaro, please make sure your .tar.gz doesn't have the .svn directory,
because if it has, and if you did a commit from there.. then the tarball
might have enough information for anyone downloading it to commit
anything
to svn...
this also means that if a friend asks you for the latest svn, direct him
to tortoisesvn, or the nightly tarball,but don't tar your own directory!
KKRT
On Fri, 12 May 2006 20:09:20 -0400, Youness Alaoui
<[EMAIL PROTECTED]> wrote:
> THE DAMN SVN IS NOW FUNCITONAL :@
> FUCKING SF SERVERS!!!! I SPENT THE WHOLE DAY ON THIS SHIT!!!!!!!!!!!!
> anyways, it's now done... please everyone, switch to svn.. it's really
> easy, you simply do :
> svn co https://svn.sourceforge.net/svnroot/amsn/trunk/amsn amsn
> or
> svn co https://svn.sourceforge.net/svnroot/amsn/trunk/amsn-extras
> amsn-extras
> or
> svn co https://svn.sourceforge.net/svnroot/amsn/trunk/www www
>
> there you go.. it's always the same, svn update, svn commit, svn diff,
> svn delete, svn add... we also have svn status, and svn move...
>
> NOTE TO ALL... PLEASE DO WHAT'S NECESSARY TO PORT TO SVN!!!!!!! I
added
> a note in IRC topic, and added a factoid in the bot, I spent around 5
to
> 6 hours doing the migration today because of the shitty SF... so
please,
> take at least care of updating the rest (the autoupdater, the www/
> module in the website, the autoupdater/ dir in the website, the cron
> jobs (Alvaro), a symlink from the amsn_cvs.tar.gz to amsn_svn.tar.gz..
> check if all is correct (no data corruption for example), etc...
change
> all references to CVS in the wiki..
> post a new annoucement in the website (we never use the site's
> newspage:S) and finally, if all is good, delete all files from the CVS
> tree and create a file MOVED with its content explaining the move to
svn
> and instructions and links on how to get it...
>
> KaKaRoTo
>
>
>
> On Fri, 12 May 2006 12:09:32 -0400, Boris Faure (aka billiob)
> <[EMAIL PROTECTED]> wrote:
>
>> I agree with Sander and Youness. It'll be good to commit (and learn
>> SVN) on a new safe base ASAP.
>>
>>> Le Friday 12 May 2006 08:31, Youness Alaoui a écrit:
>>> > It seems we'll need to be changing everything to move to the new
CVS
>>> > infrastructure...
>>> > for that specific reason, I propose we move to SVN right NOW...
>>> > GMTA : Sander had the same idea, so I guess he agrees.
>>> > what do you guys think ? i think we should just do it... cvs will
be
>>> back
>>> > tomorrow, so answer should get in max tomorrow.. once cvs is back
up
>>> and
>>> > if no real good reason for not doing it is provided, then I'll
start
>>> the
>>> > migration process... 24 hours later (max), our svn should be up
and
>>> > running, and from their, we'll do our commits...
>>> >
>>> > KKRT
>
>
>
--
KaKaRoTo
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
