Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.
You can access the repository and download snapshots at:
http://www.libsdl.org/svn.php
Enjoy!
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment_______________________________________________
SDL-announce mailing list
SDL-announce at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl-announce
Hello !
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.You can access the repository and download snapshots at:
http://www.libsdl.org/svn.php
Juhu. Great. I think for libs like SDL SVN with
Atomic Commits is a good thing. It also makes
easier handling with different branches for example
is this patch from SDL 1.2 in 1.3 or not.
CU
Hello !
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.You can access the repository and download snapshots at:
http://www.libsdl.org/svn.php
README.CVS should be
changed to README.SVN
and edited.
CU
Sam Lantinga wrote:
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.
Fantastic! Thank you Sam!
–ryan.
README.CVS should be
changed to README.SVN
and edited.
Fixed in svn revision #2217.
(ah, the real benefit of Subversion, being able to point to a single
revision number for each fix!)
–ryan.
Hello !
(ah, the real benefit of Subversion, being able to point to a single
revision number for each fix!)
Jup. Only the Web SVN browsing thing is not that good.
A better choice and more looking like the old CVSweb
is ViewVC ( http://www.viewvc.org/ )
Seeing it in action :
http://www.syntheticsw.com/~sdlgame/viewsvn.cgi/
So maybe it would be possible to install that, too.
CU
Sam Lantinga wrote:
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.
Fantastic! Thank you Sam!
You’re welcome! Thanks for suggesting it! 
-Sam Lantinga, Senior Software Engineer, Blizzard EntertainmentCongrats on the switch. Good to see the SVN revolution is going strong!On 4/26/06, Sam Lantinga wrote:
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.You can access the repository and download snapshots at:
http://www.libsdl.org/svn.phpEnjoy!
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment
–
Sam Lantinga wrote:
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.
Cool!
I just noticed that there seem to be no tags for the old releases in
/tags/, while CVS has a lot of tags like release_1_2_9. Is that intentional?
-Christian
Sam Lantinga wrote:
Simple DirectMedia Layer is now using Subversion instead of CVS
for source control.
Cool!
I just noticed that there seem to be no tags for the old releases in
/tags/, while CVS has a lot of tags like release_1_2_9. Is that intentional?
Not entirely, I wanted to strip branches, not tags, but since we have source
snapshots for each of the releases, it’s not a big deal.
-Sam Lantinga, Senior Software Engineer, Blizzard EntertainmentSam Lantinga wrote:
I just noticed that there seem to be no tags for the old releases in
/tags/, while CVS has a lot of tags like release_1_2_9. Is that intentional?Not entirely, I wanted to strip branches, not tags, but since we have source
snapshots for each of the releases, it’s not a big deal.
I stumbled on it today when I wanted to find the answer to “Was this
piece of code already present in the 1.2.9 release, or was it added
afterwards?”. Tags would be useful for this - from the tag I could get
the revision number corresponding to the release, and compare it to the
revision number when the code in question was changed.
-Christian
I stumbled on it today when I wanted to find the answer to “Was this
piece of code already present in the 1.2.9 release, or was it added
afterwards?”. Tags would be useful for this - from the tag I could get
the revision number corresponding to the release, and compare it to the
revision number when the code in question was changed.
http://www.libsdl.org/release/
-Sam Lantinga, Senior Software Engineer, Blizzard EntertainmentI stumbled on it today when I wanted to find the answer to “Was this
piece of code already present in the 1.2.9 release, or was it added
afterwards?”. Tags would be useful for this - from the tag I could get
the revision number corresponding to the release, and compare it to the
revision number when the code in question was changed.
Actually, I’d find this historically interesting for the really old
stuff and useful for future releases, and will spend some time comparing
the release tarballs and tagging the repository. I did this for
SDL_sound and PhysicsFS when moving to Subversion, and I like how it
turned out:
http://svn.icculus.org/physfs/tags/
Once the tedious sorting work is done, it makes it really nice for being
able to view various releases through ViewVC without having to sort
through tarballs.
However: we don’t have a complete history. svn revision #136 is the
initial SDL import in April 2001…I guess this is probably when the CVS
repository moved from lokigames.com to libsdl.org. The SDL_mixer (and
maybe other stuff) revisions go back to the Loki days, though…still,
we can tag SDL releases from, I think, 1.2.1 and later.
–ryan.
Actually, I’d find this historically interesting for the really old
stuff and useful for future releases, and will spend some time comparing
the release tarballs and tagging the repository.
And here are the revision numbers for SDL…
1.2.1: revision 220.
1.2.2: revision 273.
1.2.3: revision 439.
1.2.4: revision 617.
1.2.5: revision 818.
1.2.6: revision 1111.
1.2.7: revision 1297.
1.2.8: revision 1492.
1.2.9: revision 1652.
Assuming you want these to exist at…
svn://libsdl.org/tags/SDL/release-X.Y.Z
…you’d run these commands…
svn mkdir svn://libsdl.org/tags/SDL
svn cp -r 220 svn://libsdl.org/trunk/SDL
svn://libsdl.org/tags/SDL/release-1.2.1
svn cp -r 273 svn://libsdl.org/trunk/SDL
svn://libsdl.org/tags/SDL/release-1.2.2
(…etc…)
I’ll leave this until I get a greenlight from Sam, though, in case he
wants a different layout in the “tags” dir.
–ryan.
I’ll leave this until I get a greenlight from Sam, though, in case he
wants a different layout in the “tags” dir.
Green light!
One of the really nice things about subversion is that you can move tags
around.
I’ll move the existing tags into the SDL subdirectory when you’re done.
Thanks!
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment
Ryan C. Gordon wrote:
Actually, I’d find this historically interesting for the really old
stuff and useful for future releases, and will spend some time comparing
the release tarballs and tagging the repository.And here are the revision numbers for SDL…
1.2.1: revision 220.
1.2.2: revision 273.
1.2.3: revision 439.
1.2.4: revision 617.
1.2.5: revision 818.
1.2.6: revision 1111.
1.2.7: revision 1297.
1.2.8: revision 1492.
1.2.9: revision 1652.
Hey, thanks! I just started doing the same work…
I came to the conclusion that release_1_2_9 (from CVS, not the tarball)
corresponds to rev. 1653, but I may be wrong about this (have to leave now).
-Christian
I came to the conclusion that release_1_2_9 (from CVS, not the tarball)
corresponds to rev. 1653, but I may be wrong about this (have to leave now).
Yeah, that’s just the addition of a .cvsignore file over what I tagged
(revision 1652), which isn’t in the release tarball either way. It’s
close enough.
–ryan.