Hi,
A pragmatic way to do it is to do put updates on the server using:
cvs co -rRELEASE_20 proj
Then, ... To make a quick fix, get the latest source code on your dev
environment, bump up the version number in your dev environment (even on
your local machine running apache/iis/whatever). Tag it u
bobby temper wrote:
>
> Hello,
>
> Thanks for the answers.
>
> I also agree with Jim, but it might be hard to convince content people that
> they have to go throught a staging first, for simple stuff. I will definitly
> do whatever i can, tho :).
>
> Todd, what you're saying refers actually to
bobby temper wrote:
> I also agree with Jim, but it might be hard to convince
> content people that
> they have to go throught a staging first, for simple stuff.
In my experience, it's usually the simple stuff that causes the most
headaches ;=)
> I'm wondering if
> it would be better to install
OTECTED]>
To: "Jim.Hyslop" <[EMAIL PROTECTED]>
CC: "'bobby temper'" <[EMAIL PROTECTED]>, info-cvs@gnu.org
Subject: Re: best production practice?
Date: Wed, 09 Feb 2005 17:18:36 -0500
"Jim.Hyslop" wrote:
>
> bobby temper wrote:
> &
"Jim.Hyslop" wrote:
>
> bobby temper wrote:
> > What i meant is that, we have the code running on a
> > production machine. Now
> > and then, that code gets changed, and sometimes, it's content
> > gets out of
> > sync with whats on production (ie. for example. someone edit
> > directly on
> > pro
bobby temper wrote:
> What i meant is that, we have the code running on a
> production machine. Now
> and then, that code gets changed, and sometimes, it's content
> gets out of
> sync with whats on production (ie. for example. someone edit
> directly on
> production, for a hotfix (i know thi
On Wed, Feb 09, 2005 at 03:52:29PM +, bobby temper wrote:
> Hello,
>
> What i meant is that, we have the code running on a production machine. Now
> and then, that code gets changed, and sometimes, it's content gets out of
> sync with whats on production (ie. for example. someone edit direct
would like.
Best regards,
Bobby
From: Rachel Burns <[EMAIL PROTECTED]>
To: bobby temper <[EMAIL PROTECTED]>
CC: info-cvs@gnu.org
Subject: Re: best production practice?
Date: Tue, 08 Feb 2005 19:17:36 -0800
bobby temper wrote:
Hello CVS users,
The company i work for is having difficulties k
Hello bobby,
I am not sure what you mean, but I have written a litte script which
activates on "tag" commands with certain names, as I do not want every
checkin from everybody to go into the production environment.
Then it does a "cvs export", builds the sources and - if no error -
emails the s
bobby temper wrote:
Hello CVS users,
The company i work for is having difficulties keeping production and
the repository in sync'.
Not sure what you mean by production and repository in sync ? Did you
mean to say you want to have two repositories that need to be kept in sync ?
If yes you may wan
10 matches
Mail list logo
