From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20772 invoked by alias); 23 Mar 2003 16:30:00 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 20711 invoked from network); 23 Mar 2003 16:29:59 -0000 Subject: Re: [ECOS] eCOS 2.0 install vs CVS checkout From: "Gary D. Thomas" To: Tim michals Cc: eCos Maintainers In-Reply-To: <20030323162048.71964.qmail@web20907.mail.yahoo.com> References: <20030323162048.71964.qmail@web20907.mail.yahoo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-4) Date: Sun, 23 Mar 2003 16:30:00 -0000 Message-Id: <1048436998.2766.5020.camel@hermes.chez-thomas.org> Mime-Version: 1.0 X-SW-Source: 2003-03/txt/msg00053.txt.bz2 On Sun, 2003-03-23 at 09:20, Tim michals wrote: > Gary, > > Sorry for the direct email, also maybe I should > include Jonathan, but I have several issues: > - Need to release another IDT BSP ASP, should I go and > create a epk based on the new directory structure, to > help speed up the release process? > - Need to reply to IDT email about ROM support and > sumbit other fixes. Should these use the 2.0 branch > a Actually, these are "eCos maintainer" questions, so I've copied that list. nd use the new directory structure? > > Also, is the new structure using the current and > 2_0b1? > The 2_0b1 only occurs in a released branch. CVS uses "current" everywhere - trunk, branches, etc. If you really want to make something relative to the branch, then do it like this: * Check out the 2.0 branch cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos co -r ecos-v2_0-branch ecos-full * Make your patches &/or .epk relative to this These will be much easier to merge/include in the main tree. Normally, we want to see patches against the trunk. If they belong in a branch, there is an internal approval process for this where we look at the changes and then merge them as appropriate from the trunk to the branch. > > Thanks, > > tcmichals > --- "Gary D. Thomas" wrote: > > On Sun, 2003-03-23 at 09:12, Tim michals wrote: > > > Quick question on directory structure between cvs > > and > > > using the install procedure for 2.0: The install > > > creates sub directories, v2_0b1, and cvs is using > > > current. If using cvs, is this the current head > > of > > > the 2.0b1? > > > > No, you would need to use the tag > > 'ecos-v2_0b1-release' to > > get exactly that version. You can use the tag > > 'ecos-v2_0-branch' > > to keep up with the latest 2.0 branch. > > > > -- > > > .--------------------------------------------------------. > > | Mind: Embedded Linux and eCos Development > > | > > > |--------------------------------------------------------| > > | Gary Thomas email: > > gary.thomas@mind.be | > > | Mind ( http://mind.be ) tel: +1 (970) 229-1963 > > | > > | gpg: http://www.chez-thomas.org/gary/gpg_key.asc > > | > > > '--------------------------------------------------------' > > > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! > http://platinum.yahoo.com -- .--------------------------------------------------------. | Mind: Embedded Linux and eCos Development | |--------------------------------------------------------| | Gary Thomas email: gary.thomas@mind.be | | Mind ( http://mind.be ) tel: +1 (970) 229-1963 | | gpg: http://www.chez-thomas.org/gary/gpg_key.asc | '--------------------------------------------------------'