You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2004/06/28 06:19:04 UTC

moving the website to svn

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


OK, I'm planning to change the way the SpamAssassin website operates a
little; instead of its current CVS backing, I want to use SVN.
Specifically, I was planning to check the contents into
https://svn.apache.org/repos/asf/spamassassin/ somewhere. :)

How's about this -- since I don't think we can create a new "module" in
the sf.net cvs style, we create a *branch* for the website, create a
"sawebsite" dir in that branch, and put all the files in there?

(I'm trying to avoid the situation where a simple "svn co" of trunk would
wind up checking out the entire website content along with the
SpamAssassin source code.)

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFA35w4QTcbUG5Y7woRApjPAJ433imqUnL2fKVSvzbGkEEQ6nHP8wCgl2/G
19WEovrrMeOcuX94sqdu86U=
=1dJJ
-----END PGP SIGNATURE-----

RE: moving the website to svn

Posted by Sander Striker <st...@apache.org>.
> From: Daniel Quinlan [mailto:quinlan@pathname.com] 
> Sent: Monday, June 28, 2004 8:53 AM

> jm@jmason.org (Justin Mason) writes:
> 
> > OK, I'm planning to change the way the SpamAssassin website 
> operates a 
> > little; instead of its current CVS backing, I want to use SVN.
> 
> ++1
> 
> > Specifically, I was planning to check the contents into 
> > https://svn.apache.org/repos/asf/spamassassin/ somewhere. :)
> 
> +1
>  
> > How's about this -- since I don't think we can create a new 
> "module" 
> > in the sf.net cvs style, we create a *branch* for the 
> website, create 
> > a "sawebsite" dir in that branch, and put all the files in there?
> > 
> > (I'm trying to avoid the situation where a simple "svn co" of trunk 
> > would wind up checking out the entire website content along 
> with the 
> > SpamAssassin source code.)
> 
> -0.9 sounds like a kludge, I think a different directory 
> parallel to spamassassin makes more sense:
> 
>   https://svn.apache.org/repos/asf/spamassassin.web/trunk
> 
> or better:
> 
>   https://svn.apache.org/repos/apache.org/spamassassin/trunk

Nope, simply parallel to trunk is fine.  This keeps each
project self contained, and is a lot easier to manage permission
wise... :)

> and this even has the benefit of already existing:
> 
>   $ svn ls https://svn.apache.org/repos/asf/www
>   xml.apache.org/

Which shouldn't be there.


Sander

Re: moving the website to svn

Posted by Daniel Quinlan <qu...@pathname.com>.
jm@jmason.org (Justin Mason) writes:

> OK, I'm planning to change the way the SpamAssassin website operates a
> little; instead of its current CVS backing, I want to use SVN.

++1

> Specifically, I was planning to check the contents into
> https://svn.apache.org/repos/asf/spamassassin/ somewhere. :)

+1
 
> How's about this -- since I don't think we can create a new "module" in
> the sf.net cvs style, we create a *branch* for the website, create a
> "sawebsite" dir in that branch, and put all the files in there?
> 
> (I'm trying to avoid the situation where a simple "svn co" of trunk would
> wind up checking out the entire website content along with the
> SpamAssassin source code.)

-0.9 sounds like a kludge, I think a different directory parallel to
spamassassin makes more sense:

  https://svn.apache.org/repos/asf/spamassassin.web/trunk

or better:

  https://svn.apache.org/repos/apache.org/spamassassin/trunk

and this even has the benefit of already existing:

  $ svn ls https://svn.apache.org/repos/asf/www
  xml.apache.org/

Daniel

-- 
Daniel Quinlan
http://www.pathname.com/~quinlan/

RE: moving the website to svn

Posted by Sander Striker <st...@apache.org>.
> From: jm@jmason.org [mailto:jm@jmason.org] 
> Sent: Monday, June 28, 2004 6:19 AM

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> OK, I'm planning to change the way the SpamAssassin website 
> operates a little; instead of its current CVS backing, I want 
> to use SVN.
> Specifically, I was planning to check the contents into 
> https://svn.apache.org/repos/asf/spamassassin/ somewhere. :)
> 
> How's about this -- since I don't think we can create a new 
> "module" in the sf.net cvs style, we create a *branch* for 
> the website, create a "sawebsite" dir in that branch, and put 
> all the files in there?

Create a 'site' directory next to 'trunk', 'branches', and 'tags'.


Sander