[M3commit] CVS Update: cm3

[Rodney M. Bates]

I am still not sure just what you took out.  I guess I need to look at it
to be sure what I think.

As a principle, putting stuff back in later is often *far* more
difficult that one might think or than just leaving it in.  Even
with a system that preserves all the old versions, you have to
comb through many old versions/updates to see which ones are relevant.
Then you have to comb through each to see which changes are relevant.
Even if the remover kept all relevant changes in separate updates and
gave them good comments, you don't really know this, and have to review
it all.

Then you have to find where the code has moved to in the latest version.
And then the actual editing.  All this has to be done manually, and can
be very tedious. And finally, it's unusually error-prone precisely
because it's so boring, yet picky.

Note that you don't have to maintain it all in working condition.
You can disable it in various ways, at build time, runtime, etc.,
or even just comment stuff out, but leave it in the files.
Good comments as to what you have done are, of course, always
appropriate.

Jay K wrote:
> Let's put it back when we need it, if m3gdb supports such target.
>   (e.g. it doesn't support ARM_DARWIN anyway).
> Maybe by then the trees in the backen will be good enough that gdb will suffice.
> I use the recent release as a good easy source of getting older code from.
>   (easier than cvsweb, which is also available)
> 
> Or if you insist I can put it back immediately.
> 
> 
>  - Jay
> 
> 
> ----------------------------------------
>> Date: Mon, 13 Sep 2010 16:09:51 -0500
>> From: rodney_bates at lcwb.coop
>> To: m3commit at elegosoft.com
>> Subject: Re: [M3commit] CVS Update: cm3
>>
>> Not sure what you mean here. If you mean m3gdb will only be built
>> on the same machine it runs on, I think that is entirely reasonable.
>>
>> If you mean no cross-debuggers (which run on one machine and debug
>> a different one), we should preserve these. Especially with the
>> proliferation of small embedded devices, etc.
>>
>> Probably not much need to be able to build such a cross debugger
>> until somebody has a specific need, but existing separation between
>> HOST (machine gdb runs on) and TARGET (where the debugee program runs)
>> should be preserved in the code so we don't lose the work that went
>> into it.
>>
>> Jay Krell wrote:
>>> CVSROOT: /usr/cvs
>>> Changes by: jkrell at birch. 10/09/13 11:15:55
>>>
>>> Modified files:
>>> cm3/m3-sys/m3gdb/src/: m3makefile
>>> Removed files:
>>> cm3/m3-sys/m3gdb/src/: platforms.quake
>>>
>>> Log message:
>>> remove cross gdb stuff
>>>
>>>
>