From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Symbol evaluation code
Date: Wed, 13 Jun 2001 07:57:00 -0000
Message-id: <3B277F6C.7040108@cygnus.com>
References: <87hey4jbsd.fsf@dynamic-addr-83-177.resnet.rochester.edu>
X-SW-Source: 2001-06/msg00258.html

> I plan on making the push_opcode non-varargs before making anything
> use it, but i really want to get this stuff out of my tree and into
> sourceware, before I start having fun with cvs conflicts.  Also, one
> of my HD's is starting to go, and I didn't want to lose it.


(Jim B actually suggested this)

Just FYI, if people are creating a lot of expermental code then it might 
be a good idea to keep them on a CVS branch rather than in a local 
sandpit.  At least that way it is being backed up and it is available 
for others to view.

I should note though, that there is a big difference between using a 
branch to run a few experements and using a branch to create jumbo 
patches.  To give an example, I'm tinkering the MI code.  Consequently 
I've the following working directories.

	MI/src
		I'm using this to figure out
		what needs changing and how

	GDB/*	A reference directory

	WIP/*	one of my merge directories

I'm pulling changes out of the MI directory and them merging them into 
WIP before posting them.  They then get back merged in to MI.  Over time 
MI and WIP/GDB converge.  I would never submit a patch taken directly 
from my experemental MI directory since it just isn't up to scratch.

	Andrew