On Thu, Mar 13, 2008 at 6:38 PM, Sean Carolan <[EMAIL PROTECTED]> wrote:
> > I dont really think you can get much easier than CVS if you need
> > centralized management over a network. If it never gets off the
> > machine then there is RCS. If those aren't simple enough... I don't
> > think an
> Thank you, Stephan. The enormous .tar.gz is now
> easily swallowed by the CVS snake.
I mis-spelled your name, Stephen, my bad.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
"just copy it into the archive by updating CVSROOT/cvswrappers"
*.tar -k 'b' -m 'COPY'
*.tbz -k 'b' -m 'COPY'
*.tgz -k 'b' -m 'COPY'
This worked great. Thank you, Stephan. The enormous .tar.gz is now
easily swallowed by the CVS snake.
___
CentOS
Sean Carolan wrote:
I have run into a snag with my CVS installation:
[EMAIL PROTECTED]:~]$ cvs co -P installfiles
cvs checkout: Updating installfiles
cvs [checkout aborted]: out of memory; can not allocate 1022462837 bytes
Unfortunately we have a couple of large binary .tgz files in the
reposit
Sean Carolan wrote:
> Checking in binary files into CVS or any repository control system is
> usually a broken thing. You want to either check in the stuff inside
> the tar ball seperately (if its going to change), or just copy it into
> the archive by updating CVSROOT/cvswrappers
This come
> Because these tools are meant to deal with source code files and deal
> with diffs of such files. You are cramming a 1 gigabyte of compressed
> bits at it and its trying to make sure it could give you a diff of it
> later on. I don't have any idea why you would want to store it in a
> CVS ty
On Thu, Mar 13, 2008 at 3:03 PM, Sean Carolan <[EMAIL PROTECTED]> wrote:
> > > Checking in binary files into CVS or any repository control system is
> > > usually a broken thing. You want to either check in the stuff inside
> > > the tar ball seperately (if its going to change), or just copy i
> > Checking in binary files into CVS or any repository control system is
> > usually a broken thing. You want to either check in the stuff inside
> > the tar ball seperately (if its going to change), or just copy it into
> > the archive by updating CVSROOT/cvswrappers
This comes back to the p
Stephen John Smoogen wrote:
> On Thu, Mar 13, 2008 at 1:49 PM, Sean Carolan
> <[EMAIL PROTECTED]> wrote:
> > I have run into a snag with my CVS installation:
> >
> > [EMAIL PROTECTED]:~]$ cvs co -P installfiles
> > cvs checkout: Updating installfiles
> > cvs [checkout aborted]: out of memory; c
On Thu, Mar 13, 2008 at 1:49 PM, Sean Carolan <[EMAIL PROTECTED]> wrote:
> I have run into a snag with my CVS installation:
>
> [EMAIL PROTECTED]:~]$ cvs co -P installfiles
> cvs checkout: Updating installfiles
> cvs [checkout aborted]: out of memory; can not allocate 1022462837 bytes
>
> Unfor
> Try upping your ulimit.
> What does "ulimit -a" give.
[EMAIL PROTECTED]:~]$ ulimit -a
core file size(blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 4
max memory size (kbytes, -m) unlimited
Sean Carolan wrote:
I have run into a snag with my CVS installation:
[EMAIL PROTECTED]:~]$ cvs co -P installfiles
cvs checkout: Updating installfiles
cvs [checkout aborted]: out of memory; can not allocate 1022462837 bytes
Try upping your ulimit.
What does "ulimit -a" give.
--
Milton Calnek
g list
Subject: Re: [CentOS] Good version control package?
I have run into a snag with my CVS installation:
[EMAIL PROTECTED]:~]$ cvs co -P installfiles
cvs checkout: Updating installfiles
cvs [checkout aborted]: out of memory; can not allocate 1022462837 bytes
Unfortunately we have a couple of large
I have run into a snag with my CVS installation:
[EMAIL PROTECTED]:~]$ cvs co -P installfiles
cvs checkout: Updating installfiles
cvs [checkout aborted]: out of memory; can not allocate 1022462837 bytes
Unfortunately we have a couple of large binary .tgz files in the
repository. I was able to ch
Sean Carolan a écrit :
We have a directory full of installation and configuration scripts
that are updated on a fairly regular basis. I would like to implement
some sort of version control for these files. I have used SVN and CVS
in the past, but I thought I'd ask if anyone can recommend a simp
> I dont really think you can get much easier than CVS if you need
> centralized management over a network. If it never gets off the
> machine then there is RCS. If those aren't simple enough... I don't
> think any of the others are going to help.
Thanks for the pointers, it looks like we will
On Thu, Mar 13, 2008 at 10:39 AM, Sean Carolan <[EMAIL PROTECTED]> wrote:
> We have a directory full of installation and configuration scripts
> that are updated on a fairly regular basis. I would like to implement
> some sort of version control for these files. I have used SVN and CVS
> in th
Sean Carolan wrote:
We have a directory full of installation and configuration scripts
that are updated on a fairly regular basis. I would like to implement
some sort of version control for these files. I have used SVN and CVS
in the past, but I thought I'd ask if anyone can recommend a simple,
We have a directory full of installation and configuration scripts
that are updated on a fairly regular basis. I would like to implement
some sort of version control for these files. I have used SVN and CVS
in the past, but I thought I'd ask if anyone can recommend a simple,
easy-to-use tool that
19 matches
Mail list logo
