public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jens.ohlund@secrc.abb.se
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GCC and INSIGHT, snapshots
Date: Wed, 12 Jul 2000 22:57:00 -0000	[thread overview]
Message-ID: <OFC4CBDC53.1973D8E0-ONC125691B.0020ACDE@secrc.abb.se> (raw)

Hi !

Lets see if I understood you right :)

For time beeing I DON'T have to patch the latest gcc/insight snapshots, just build them and go ?

yours
Jens





ecos-discuss-owner@sources.redhat.com
2000-07-13 01:59


To:   bartv@redhat.com
cc:   jens.ohlund@secrc.abb.se, ecos-discuss@sourceware.cygnus.com
Subject:  Re: [ECOS] GCC and INSIGHT, snapshots

Security Level:?         Internal


Bart Veer wrote:
>
> >>>>> "Jens" == jens ohlund <jens.ohlund@secrc.abb.se> writes:
>
>     Jens> Just for the curiosity, when I build the gcc and insight, am
>     Jens> I to apply the patches as well IF i have the latest
>     Jens> snapshots of the gcc and insight ?
>
> Unfortunately keeping track of the latest snapshots of gcc, binutils,
> and gdb would require a lot of effort. Hence the eCos team prefers to
> concentrate on the latest official releases of these tools when
> possible - that leaves more time for actually working on eCos.

I should point out here that in the cases where we say to apply some
patches, you should apply them. Not all the patches that are to be applied
are going to be submitted for inclusion in the main sources. Right now,
there are no patches waiting to be checked into the main gcc/binutils/gdb
repositories that _should_ be checked in.

We try to track the snapshots if we can, and try to adjust the patches if
they break. But we would like to know if they do break, obviously! We can't
track the repositories every time someone checks something in. Letting us
know is the responsibility of the entire eCos community :-).

Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault





             reply	other threads:[~2000-07-12 22:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 22:57 jens.ohlund [this message]
2000-07-12 23:00 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2000-07-13  3:52 jens.ohlund
2000-07-13  8:00 ` Jonathan Larmour
2000-07-13  3:08 danish iftikhar
2000-07-12 23:29 jens.ohlund
2000-07-12 23:38 ` Jonathan Larmour
2000-07-12 23:15 jens.ohlund
2000-07-12 23:19 ` Jonathan Larmour
2000-07-05  8:10 jens.ohlund
2000-07-05 10:52 ` Bart Veer
2000-07-12 16:59   ` 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=OFC4CBDC53.1973D8E0-ONC125691B.0020ACDE@secrc.abb.se \
    --to=jens.ohlund@secrc.abb.se \
    --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).