public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: bothner@cygnus.com, egcs@cygnus.com
Subject: Re: Successful Build and Install
Date: Sat, 04 Apr 1998 14:20:00 -0000	[thread overview]
Message-ID: <4117.891555714@hurl.cygnus.com> (raw)
In-Reply-To: <199803311735.JAA15334@atrus.synopsys.com>

  In message < 199803311735.JAA15334@atrus.synopsys.com >you write:
  > I wrote:
  > 
  > >   > It seems that we would only want:
  > >   > * reports of failures on systems we believe to work
  > >   > * reports of successes *or* failures on systems we haven't tested.
  > 
  > Jeff writes:
  > > This is probably the right general direction for minor releases.
  > > 
  > > However at each major release it's probably useful to get these
  > > reports for all systems -- including those we regularly work on.
  > 
  > Just the same, I'd like to cut down on email volume.  We can expect
  > the egcs user community to increase greatly with time.  Do you want
  > every single egcs user on Linux to send a mail to everyone on the list,
  > saying essentially the same thing?  You'll start to drive away developers.
  > People have other things they want to do with their lives than read egcs,
  > and if they try using filters they'll miss important messages (delete
  > all test results?  what if some expose problems?).
Actually, if you're looking that far into the future, the solution
is a web page :-)  Have a little form that you can fill out to specify
what platform you built on, and maybe comments.

That info is then make available on another page -- the idea is to
cut down on the "was anyone able to build on xyz" kinds of questions.

In fact, if someone wants to contribute the html gunk to do this it
would be greatly appreciated.  Note you can check out the web pages
via CVS these days :-)

  > Another alternative is to publish a summary of test results on platforms
  > that we have tried.  We can then ask people to send in a report if their
  > results differ *and* they've checked a FAQ to make sure they haven't made
  > a common mistake.  If we have no report for their system, we would use
  > whatever users send in.
Similarly -- we'd make a set of "baseline" test results available for
releases on major platforms (I don't think it's worth the time for
snapshots).  People could then compare their own with those on the
web.

jeff

  reply	other threads:[~1998-04-04 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-25 23:43 Per Bothner
1998-03-26 18:14 ` Joe Buck
1998-04-02 11:32   ` Jeffrey A Law
1998-04-02 11:32     ` Joe Buck
1998-04-04 14:20       ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-09  9:30 successful build and install Jiří Vymazal
2002-05-24 10:21 Benjamin Collar
2002-05-24 11:22 ` Janis Johnson
1998-08-17 23:32 Successful Build and Install S. Colin Leister
1998-03-24 20:58 Pete Willemsen

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=4117.891555714@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=bothner@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=jbuck@synopsys.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).