Date: Fri, 07 Oct 2011 12:36:27 -0700 From: David Romano <unobe@cpan.org> To: freebsd-doc@freebsd.org Cc: doceng@FreeBSD.org Subject: Re: Conversion to SVN Message-ID: <4E8F54BB.4000206@cpan.org> In-Reply-To: <20111007141312.GJ26743@acme.spoerlein.net> References: <20111007141312.GJ26743@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/07/2011 07:13, Ulrich Sp=F6rlein wrote: > it looks like I'm not the only one thinking about moving the doc/www > repos from CVS to SVN, and other people actually have not only thought > about it but already played around with conversions. > > gavin did some preliminary conversions and it turns out that we end up > with ~50k revisions and about 650MB of changes (IIRC). There are also > lots of weird branches, so perhaps we could size that down a bit. > > What I, personally, would like to see is us using the same svn repo as > src. That means we would have to stop svn.freebsd.org for the > conversion, turn off email sending, dump 50k revisions into it (under > /doc and /www perhaps? where should branches/tags end up?), then turn > everything back on. > > I haven't really thought that through to the end, but setting up a > separate svn repo just seems silly to me and is another administrative > overhead. ports might be special enough (due to sheer size) to justify = a > separate repo/machine, but not doc/www. > > Please discuss and share your experiments and thoughts. I'm a new kid on the block but I'm curious why git is being overlooked=20 for the new repository. Just because it's a distributed VCS doesn't mean=20 that it can't be used like SVN. I started with SVN, then moved to SVK=20 for a spell, and dabbled in darcs before I tried out git. In my=20 experience as a developer, it's been much easier to merge changes and=20 keep track of branches/tags. Branching/tagging isn't an expensive=20 operation in git because git focuses on content changes, not file=20 changes. Not to get too off-base, but this can *definitely* help with=20 having clear documentation for a specific version of FBSD. There is=20 currently a FBSD git repo for src/ and ports/ hosted on github.com if=20 some developers haven't heard of it and are interested in seeing how its=20 capabilities can help the FBSD community. - David --=20 David Romano .:. unobe@cpan.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E8F54BB.4000206>