public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Dan Conti" <danc@iobjects.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Modify the sources in eCos packages
Date: Mon, 21 May 2001 11:23:00 -0000	[thread overview]
Message-ID: <DDD5120AE861E8458E06B6135BEF1CDE01A874@bunker.iobjects.com> (raw)

A better question might be when the eCos team plans on releasing 7312
support, since they (should) already have a patch for it. I think there
was a post on this a while back where they said there was a review
process that had to occur first.

I haven't used cvs in a while, but i would guess that you could get the
tip of the eCos cvs tree, merge your changes into the new tree, and just
use that.

-Dan

> -----Original Message-----
> From: honda@itri.org.tw [ mailto:honda@itri.org.tw ]
> Sent: Monday, May 21, 2001 12:43 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Modify the sources in eCos packages
> 
> 
> I'm trying to port the eCos on the Cirrus Logic EDB7312. By 
> the way, I've
> to add on option the configuration tools. Thus I modified the 
> CDL file.and
> the sources in the packages. But it results that I cannot 
> check out the new
> code. Is there any better way to maintain the code?
> 
> Thanks
> 
> HONDA
> Kuang-Yang Chuang
> 
> OES / ITRI
> J220, Bldg. 78, 195-8, Sec. 4, Chung-Hsing Rd.
> Chutung, Hsinchu 310, Taiwan, ROC
> 
> TEL: 886-3-5917546
> FAX: 886-3-5917531
> 
> 
> 
> 
> 
> 
> 

             reply	other threads:[~2001-05-21 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 11:23 Dan Conti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-21  0:29 honda
2001-05-21  7:18 ` Jonathan Larmour

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=DDD5120AE861E8458E06B6135BEF1CDE01A874@bunker.iobjects.com \
    --to=danc@iobjects.com \
    --cc=ecos-discuss@sources.redhat.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).