public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Brendan Simon <brendan@dgs.monash.edu.au>
To: egcs mailing list <egcs@egcs.cygnus.com>,
	binutils <binutils@sourceware.cygnus.com>,
	gdb <gdb@sourceware.cygnus.com>,
	newlib <newlib@sourceware.cygnus.com>
Subject: Sourceware synchronisation.
Date: Mon, 02 Aug 1999 19:14:00 -0000	[thread overview]
Message-ID: <37A650C1.30AFAC2A@dgs.monash.edu.au> (raw)

Now that the sourceware CD is available quarterly, I was wondering what
the chances are of synchronising new releases of sourceware projects
(binutils, gcc, newlib & gdb are the ones that mainly interest me.  I'm
not sure what else is on the sourceware CD as I do not have one yet).

I would be nice to have the latest sourceware which have been
synchronised with other sourceware releases.  The definitions of
"synchronise" is pretty open but I would like it to mean "tested and
recommended".  eg.  The latest release of binutils, gcc, newlib and gdb
that are recommended to work with each other with the least amount of
building problems.

I know this is a big ask and it is nearlyy impossible, but I think it
might be worth some effort.  Can various sourceware projects work
together in some way.  I'm sure there is some informal collaberation
between projects but it is just a guess.  Obviously this would only
apply to projects that have some dependencies on other projects.

Any thoughts,
Brendan Simon.


             reply	other threads:[~1999-08-02 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-02 19:14 Brendan Simon [this message]
1999-08-02 19:27 ` Jason Molenda
1999-08-03  9:36 ` Joe Buck

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=37A650C1.30AFAC2A@dgs.monash.edu.au \
    --to=brendan@dgs.monash.edu.au \
    --cc=binutils@sourceware.cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=newlib@sourceware.cygnus.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).