OT: How do people set up long term development

[Michael Meissner]

On Wed, May 28, 2003 at 05:07:19PM +0200, Jakub Jelinek wrote:
> On Wed, May 28, 2003 at 11:02:11AM -0400, Michael Meissner wrote:
> > I am wondering how people outside of Red Hat do long term development of
> > compiler tools when you can't check the machine specific sources into the FSF
> > repository until the NDA on the machine has been lifted?  The intention is that
> > when the chipset I am developing the GNU toolchain for is formally announced, I
> > will submit the files to the FSF for consideration of inclusion in the
> > releases, and non-machine specific changes that I make will be contributed as
> > they are written.
> > 
> > I can see three different development models:
> > 
> > 1) Create my own CVS repository of a checked out releases, and check the files
> >    into there.  Every so often, I will do a merge from the FSF sources to my
> >    own repository.  This is how we did development at OSF, Cygnus, and Red Hat.
> >    The problem is doing the merge step, and there isn't a direct correlation
> >    between the versions in the master repository and my system.  If all of the
> >    tools had CVS tags for nightly snapshots, it would make things easier, but
> >    the bintuils directories don't seem to have snapshot tags.  This is the way
> >    I'm leaning, since it will allow me to work on two systems (desk system,
> >    laptop) and using cvs to do the update.
> 
> cvs update -jgcc-3_3-branch:2003{0517,0528} works IMHO just fine, you don't
> need any nightly tags for it. All you need is to remember what was the last
> date you did a cvs merge at, which can be recorded e.g. in the CVS commit
> messages.

Thanks.

Wouldn't it have problems if there was a commit that occured around midnight,
particularly a multi-file commit, one file being committed before midnight, and
the other after midnight.

-- 
Michael Meissner
email: gnu@the-meissners.org
http://www.the-meissners.org