Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2001:
[Freeciv-Dev] Re: Managing Long-Term Changes
Home

[Freeciv-Dev] Re: Managing Long-Term Changes

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Managing Long-Term Changes
From: Adam Olsen <rhamph@xxxxxxxx>
Date: Fri, 21 Dec 2001 04:42:22 +0000

On Fri, Dec 21, 2001 at 03:36:33AM +0100, Petr Baudis wrote:
> Dear diary, on Fri, Dec 21, 2001 at 02:39:53AM CET, I got a letter,
> where Chris Richards <chrisr@xxxxxxxxxxxxxxxx> told me, that...
> > How do ya'll manage long-term changes?
> Badly. Why? :)
> 
> > Is this at all accurate?  If it is, have you considered using cvs branching
> > to do that?  (For example, branching for "generalized improvements".)  When
> > it is complete (or near enough as open-source gets), then re-merge the 
> > branch
> > back into the main dev line.
> Proposed, considered, vanished. And relatively short ago, I recommend you
> scanning archives briefly next time ;).
> 
> No mere mortal knows reason why it vanished and why it wasn't considered more
> seriously, so until someone will press shift+R here, we will continue in our
> quiet life with "stable code base" and "little between versions patches" and
> "calm CVS tree" and change the tiny bits with sluggish speed ;-).

Personally, I have no great love for CVS.  Small patches aren't worth
a branch, and large patches that do end up being eternally out of sync
with the main branch.  I'd be more likely to put the diff itself in
CVS. :)


-- 
Adam Olsen, aka Rhamphoryncus


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