[ECOS] Managing eCos modifications

[Gary Thomas]

Paul D. DeRocco wrote:
>> From: Andrew Dyer [mailto:amdyer@gmail.com]
>>
>> What I did (when I was keeping up with ecos diligently) is check out
>> copies of the ecos tree to a local directory, then check them in to
>> our local CVS server as a 'vendor branch' with a tag specifying the
>> checkout date.  our local CVS would then keep track of our local
>> changes and help with merging.
>>
>>
> http://cvsbook.red-bean.com/cvsbook.html#Tracking%20Third-Party%20Sources%20
> (Vendor%20Branches)
>> explains it.
> 
> Thanks. Looks like I need to learn a lot more about CVS. Since I'm only
> using it as a way to get eCos, not maintain my own personal source files, I
> had hoped I wouldn't have to, but I suppose it's a useful thing to know
> anyway.

Doing any sort of software development, especially one that
is tied in any way to outside sources that are also changing,
simply *requires* using proper tools like CVS, SVN or other
Source Code Management tool.  Operating without it is like
trying to drive your car without using the steering wheel.
Depending on where you live and the terrain, it might work
for a while, but sooner or later you'll end up in the ditch!

BTW, these tools have been in common practice for many years.
RCS, the predecessor of CVS, was developed by Walter Tichy in
the late 70's, shortly after he stole/acquired my office at
Purdue...

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss