[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netatalk-devel
Subject:    Re: [Netatalk-devel] Musings over the code (was Re: Netatalk
From:       Simon Bazley <simon () eyeeye ! com>
Date:       2002-12-13 3:09:40
[Download RAW message or body]

> > Since we're not proprosing to break the existing code, or even work in the same \
> > directories (at least initially) I don't see the point in making more branches.  \
> > CVS HEAD is essentially the development tree.  If you're making changes to the \
> > development tree, then surely HEAD should house them.
> 
> It certainly depends on what we intend to do; if we plan to refactor the
> code one bit at a time without ever breaking the existing setup (the
> latter is non-trivial), we can use the trunk. If there are intrusive
> changes that would break the code, we should branch. Of course a
> combination of these two methods can be used: When doing intrusive
> changes, do them in a branch. If these changes are finished, merge.
> 
> - Sebastian

Agreed, but I'm hoping its not as non-trivial as you think, as long as we use the \
existing codebase as an example of how to do it, rather than as something we're going \
to be working on.  Having the benefit of hindsight is always a help.

Simon



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Netatalk-devel mailing list
Netatalk-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netatalk-devel


[prev in list] [next in list] [prev in thread] [next in thread]