[leaf-devel] Subversion

2005-05-10 Thread Mike Noyes
Everyone,
This is a query to prepare us for the eventual move of SF to SVN.

How many people have experience with SVN? I need some good resources for
training, and some suggestions on repository structure.

-- 
Mike Noyes mhnoyes at users.sourceforge.net
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs



---
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393alloc_id=16281op=click

___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] Subversion

2005-05-10 Thread Charles Steinkuehler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Noyes wrote:
| Everyone,
| This is a query to prepare us for the eventual move of SF to SVN.
|
| How many people have experience with SVN? I need some good resources for
| training, and some suggestions on repository structure.
Subversion *ROCKS*!!!   :)
You can typically use the same repository layout you'd use for CVS,
differences that might affect how we want to arrange things:
- - We can move stuff around in subversion ourselves (no more SF support
requests for moving directories!)
- - Copies are 'cheap', so making branches/tags (they're the same in svn) is a
fast operation, no matter how big the repository gets.
- - Subversion *NEVER* modifies your files, so we can check in things like
*.lrp files, iso images, etc. without having to worry about using the right
command-line switches to make sure the files don't get mangled by EOL
replacement, tag expansion, or similar issues with CVS.  Subversion *DOES*
know about mime-types (it's a property that gets stored along with the
file), but it's typically not a major problem if this gets set incorrectly,
as the file contents are *NEVER* altered (so you can always tweak the
mime-type property later if it's wrong).
We're not exactly using CVS for revision control, so our main 'architecure'
is in the layout of the directory structure, which should probably stay the
same in svn.  One big plus will be the ability to copy (snapshot) chunks of
the svn tree into a releases area (or similar) when a particular branch (ie:
bering or Bering-uClibC) has a release.
- --
Charles Steinkuehler
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFCgPJOLywbqEHdNFwRAgc7AKDpdusqFUMMA/EWojtu+Vbfrtnx1QCg3Mml
n3kXCUeWnWXpxzTGNGrZXeY=
=AGoO
-END PGP SIGNATURE-
---
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393alloc_id=16281op=click
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel