On Mon, 11 Sep 2006 22:37:04 -0700, Mark Wedel wrote:
What I think I'll probably do is only import the main trunk from CVS.
There
really isn't any reason to import any of the branches - those will still
exist
in CVS, and I don't think any of them are active.
That's what I figured.
flex files that generate .c (loader.c) - not a big space user, yet at the
same time, pretty trivial for most people to generate (probably any system
that has gcc can pretty easily install flex if not already there). The
flex files do not change very often. The one question might be windows
On Tuesday 12 September 2006 07:35 Mark Wedel wrote:
Actually, from what I gather, it seems unlikely someone would do a svn
checkout at the top of the repository.
The reason being is that if you do that, you'll also get all the
branches, which would amount to a pretty huge amount of data.
Nicolas Weeger (Laposte) wrote:
rebuilt lib files (Archetypes, images, etc): These are the files I'm most
inclined to leave out of SVN. The images tend to be quite big (slowing
down updates). Plus, the updates are rather inconsistent - they are not
updated after every change is made to an
Alex Schultz wrote:
SVN doesn't have a concept of modules, instead it would simply be
directories containing each, but one can check out an individual
directory just as easily as if it was a module, and acts for most
intents as a module. Due to that, a the revision number would increment
as
Mark Wedel wrote:
Another question for everyone:
It has been commented/asked several times in the past whether the
automatically generated files should be in the repository, or if it should be
up
to the developer to rebuild them. There are several types of files, and my
general
Christian Hujer wrote:
On Tuesday 12 September 2006 07:35 Mark Wedel wrote:
Actually, from what I gather, it seems unlikely someone would do a svn
checkout at the top of the repository.
The reason being is that if you do that, you'll also get all the
branches, which would amount to a
7 matches
Mail list logo
