This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Keeping 2.0 source tree up to date


On Mon, Sep 22, 2003 at 01:29:28PM -0600, Gary Thomas wrote:

> What I do is have my own CVS server (repository).  Then, at
> certain times such as starting a new project, I merge the
> public CVS to the trunk of my local tree.  I then tag it and
> work from there - all local. That way, I have an exact copy of
> the public tree I started from, as well as any changes I needed
> to make for the project.  If/when it makes sense, I can then
> also push my local changes back to the public tree.

That's definitely the right way to do it.  I've just been
reading up on CVS "vendor" tags" which appear to be designed
for just such situations.  

Unfortunately, I'd still have to use MS VSS as well as local a
CVS repository, but that's another issue.

-- 
Grant Edwards
grante@visi.com

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]