In my opinion this sounds more like a coding issue than a source control issue,
unless I am misunderstanding you. I don't think svn should be used to control
the contents of your files. You need to make the script generic so one version
will work for all versions of RHEL. Then you may control
the least effort and most efficient
upgrade.
Just wanted some advice about the easiest way to accomplish my task. Thx a
bunch.
KM
--- On Thu, 3/31/11, Bob Archer wrote:
From: Bob Archer
Subject: RE: Advice on upgrading svn and moving to new server
To: "Nico Kadel-Garcia" , "Da
/glassfish SW and set it up for svn.
Since I also use Mantis - the php would also be taken care of at the same time
this way just curious.
Thanks in advance for any advice.
KM
k ahead in case.
--- On Wed, 11/3/10, David Weintraub wrote:
From: David Weintraub
Subject: Re: simple question on branching
To: "KM"
Cc: "svn-apache-users-list"
Date: Wednesday, November 3, 2010, 10:36 AM
On Wed, Nov 3, 2010 at 9:44 AM, KM wrote:
>
> We don&
ead.
Probably a silly question - but it's good to have input from others who branch
and merge regularly.
Thx for any help. If it matters - we are still on svn 1.4.3.
KM
thout downloading all of
the individual pieces and working on them.
i am going to be running Solaris 10 when I do this. I also want svn 1.5.x or
later?
Any info/help is appreciated.
KM
... just don't
have the resources or time now.
thx -
KM
