[Top][All Lists]

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

RE: Bespoke Customisations

From: Arthur Barrett
Subject: RE: Bespoke Customisations
Date: Fri, 19 Oct 2007 18:19:59 +1000

Robbie Hughes,

I suggest you get one of the (many) good books out there about CVS.

You should pay particular attention to the sections on Branching and
also Vendor Branches.

If you are using CVSNT (GPL/Free, unix,linux,windows etc) it also has
"magic branches" that is described in the eBook "All About CVS" that I
had a hand in writing.


Arthur Barrett

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of address@hidden
> Sent: Thursday, 18 October 2007 8:03 PM
> To: address@hidden
> Subject: Bespoke Customisations
> Apologies for what may be a stupid question, but i've just wasted 40
> mins googling this and still can't find an answer. I was wondering
> if someone here might be able to point me in the right direction. I
> feel like a bit of an idiot asking this as this must be a common
> problem and i can't believe i can't find a solution already.
> We've got a 300k line php5 based database system that we roll out to
> clients. We have a head trunk which works fine right up to the point
> where clients want specific (often small) mods done - little things
> like naming conventions etc.
> Currently what we have to do in an update is manually redo all the
> mods on each system before pushing them out. Sometimes we miss things
> and this can cause confusion.
> Does anyone know of a decent way of maintaining these mods so that we
> can push out an update to HEAD and the update will then 'ripple'
> through the various other branches with each maintaining their
> existing mods (assuming, presumably, that they don't conflict)
> any and all help appreciated.
> r
> --
> Robbie Hughes

reply via email to

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