From: "Gary D. Thomas" <gary.thomas@mind.be>
To: Tim michals <tcmichals@yahoo.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [ECOS] eCOS 2.0 install vs CVS checkout
Date: Sun, 23 Mar 2003 16:30:00 -0000 [thread overview]
Message-ID: <1048436998.2766.5020.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20030323162048.71964.qmail@web20907.mail.yahoo.com>
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" <gary.thomas@mind.be> 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 |
'--------------------------------------------------------'
next parent reply other threads:[~2003-03-23 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030323162048.71964.qmail@web20907.mail.yahoo.com>
2003-03-23 16:30 ` Gary D. Thomas [this message]
[not found] <20030323164025.45130.qmail@web20909.mail.yahoo.com>
2003-03-23 16:43 ` Gary D. Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1048436998.2766.5020.camel@hermes.chez-thomas.org \
--to=gary.thomas@mind.be \
--cc=ecos-maintainers@sources.redhat.com \
--cc=tcmichals@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).