[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #19822] cvs update -I don't ignore files properly

From: Marc-André Boucher
Subject: [bug #19822] cvs update -I don't ignore files properly
Date: Tue, 08 May 2007 18:48:56 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070309 Firefox/

Follow-up Comment #2, bug #19822 (project cvs):

Thanks a lot for the quick answer!
I totally forgot about that, thanks for pointing it out. I'm sure you saw my
next question coming, but anyway :
Is there a way to ignore files that are known to CVS then? The problem is I
want to deploy my project to multiple servers/environments/sites, but I don't
want to override the configuration files every time I create my deployment
I have a single directory with my project which I update using CVS, and
multiple directories with the configuration files of each of the
servers/environments/sites where I deploy.

I would like to run a single "cvs update" command to keep the project
up-to-date, but ignoring the config files so that I don't have to modify them
everytime they are committed in CVS.

I have modified them directly on the deployment server, and they merge
everytime I update the project, which is ok, but if the configuration files
are committed for some changes, I don't want them to merge : I'm gonna modify
them manually if I have to.

I know it almost seems like a software deployment problem, but the CVS part
is the heart of it. I have found other ways to do this, but they're too much
of a "patch" than a real solution!

Thanks again for your time. If there's a way to do this, that would spare me
some problems!


Reply to this item at:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]