This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Keeping 2.0 source tree up to date
- From: "Reinhard JESSICH" <Reinhard dot JESSICH at frequentis dot com>
- To: <gary at mlbassoc dot com>,<grante at visi dot com>,<roland dot cassebohm at visionsystems dot de>
- Cc: <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 29 Sep 2003 18:32:14 +0200
- Subject: Re: [ECOS] Keeping 2.0 source tree up to date
>>> Roland Caßebohm <roland.cassebohm@visionsystems.de> 09/29/03 05:50pm >>>
<snip>
> > we import from the local copy of the annon CVS to our main branch "cvs
> > import vendor-tag release-tag". We do this at least once in two months, to
> > keep track of the ongoing development.
> Is vendor-tag everytime the same, or do I have to rename it everytime I call
> cvs import?
> With release-tag I will do somthing like release-yyyy_mm_dd, but I'm not
> sure what to do with the vendor-tag.
The vendor-tag have to be the same for several imports.
We use "ecos-2-0-repo" and "ecos-ddmmyy" for the release-tag.
If there will be an ecos-3.0 version in the future, we will use "ecos-3-0-repo" as
vendor-tag. But then we have to import it to an other branch. So you will need the
-b option for cvs import. cvs import uses -b 1.1.1 as the default. If you will not use
-b 1.1.2 for the new branch, cvs will import it to the 1.1.1 branch, which is
"ecos-2-0-repo". Using -b is necessary, because cvs doesn't use the vendor-tag to find the
right branch.
BR
Reinhard
--
Ing. Reinhard Jessich Phone: +43/1/81150/2395
Software Design Fax: +43/1/81150/3169
Frequentis Nachrichtentechnik GmbH A-1120 Wien, Spittelbreitengasse 34
http://www.frequentis.com eMail: reinhard.jessich@frequentis.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