On Sat, 28 Jan 2006 01:15:07 -0500, Jérôme Gagnon-Voyer
<gagnonje5000@xxxxxxx> wrote:
First of all we need sourceforge to fully support Subversion,
Yes!!! for many obvious reasons, but mainly, we also want to be able to
keep our amsn-commits thing and CIA running on our commits... if we loose
amsn-commits, then we don't migrate, even if SF says it's stable...
I don't
know if it's the case but it's very important. NO we don't want to
move to something else. "Hey my name is Yves #2 and I can host your
SVN server" NO!!!!!
euhh.. did you really need to mention it? I don't think anyone will accept
anyways!
BTW, can someone just tell the big differences betwen subversion and
CVS?
as I said, snapshot revision.. which means, you will commit a gui.tcl,
then you'll have "svn revision is 111", then commit protoco.tcl and you'll
have "svn revision is 112".. so if you go and checkout revision 112,
you'll get the whole svn snapshot at that time... while in cvs, you do a
commit, you'll have file gui.tcl at revision 112, protocol.tcl at revision
250, chatwindow.tcl at revision 28... you can't tell someone "download
revision 112", you'll have to tell him "download revision 112 of gui.tcl,
250 of..." OR give exact date, time (a la seconde pres) of the snaphost
you want him to checkout...
also, if you want to rename a file, you do "svn rename capture.c
capture-nong.c" (for example) and you keep the whole history of the file
(now, capture-nong.c has no history before the rename, and capture.c has
the history of the capture extension when it was capture.c and the history
of the libng version).. this means, history, etc.. are managed per file,
not per filename..
Forgot it, just read it on wikipedia
:P
Atomic commits. Interrupted commit operations do not cause repository
inconsistency or corruption.
Renamed/copied/removed files retain full revision history.
Native support for binary files, with space-efficient binary-diff
storage.
Directories are versioned. Entire directory trees can be moved around
and/or copied very quickly, and retain full revision history.
Constant-time branching and tagging.
Optimized repository accesses. This reduces unnecessary network
traffic to the repository host.
yep.. easier, but not always clear!
Le 28 janvier 2006 à 00:03, Youness Alaoui a écrit :
I already worked with subversion and didn't see much of a
difference (apart from 'snapshot' revisioning instead of file
revisioning).. I did understand though from what people said, that
it is better (tried it almost 3 years from now and it was a bit
unstable at that point though.. i'm sure it's better now).
Since I don't see a huge difference in cvs/svn, I mean difference
as in 'a month of training for all devels just to be able to use
svn correctly without screwing up everything', I say go for it.
Question is : SF gives svn support.. but is it official full
support or was it "we're trying to get svn working, can people use
it and see if we set it up correctly".. I wouldn't want them to be
still trying to set it up and we end up with loosing all commits
done on SVN... (are the 2 synced or do we drop cvs completly when
we switch to svn ?)
in any case, let's just make sure svn is fully supported by SF, and
let's do the switch!
KaKaRoTo
On Fri, 27 Jan 2006 21:13:42 -0500, GrdScarabe
<grdscarabe@xxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think Sourceforge is beginning to offer Subversion service. I
think
branching is easier and cleaner in subversion. Should we try to
move to
subversion?
Subversion has for sure a lot of improvements ... GNA has proprosed a
subversion service for several months now, and that's really a
pleasure
to use it !
So if we have to vote for subversion, I r ... now there is for sure
persons more experienced than me about cvs and subversion, than can
provide more arguments :)
GrdScarabe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD2tNWPmfsnt4Id3wRAshuAKC8H85ixx28jTrCLluQSLkHu+15UQCgiUm9
+VuhoncorRhXsgdLDGHFfr0=
=F6LW
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through
log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through
log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD
SPLUNK!
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
