From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: bothner@cygnus.com (Per Bothner), egcs@cygnus.com
Subject: Re: Successful Build and Install
Date: Thu, 02 Apr 1998 11:32:00 -0000 [thread overview]
Message-ID: <1236.891365158@hurl.cygnus.com> (raw)
In-Reply-To: <199803261957.LAA15374@atrus.synopsys.com>
In message <199803261957.LAA15374@atrus.synopsys.com>you write:
> 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.
>
> So we should be telling folks something like: if you run X, Y, or Z,
> let us know if the install fails or there are large numbers of test
> failures. If you have something more exotic, we'd appreciate a report
> if you build successfully. And the list can be dynamic: if we hadn't
> verified, say, FreeBSD 2.2.6 but some user does, we can indicate that.
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.
It's been my experience that as a developer I know how to build
things dead cold. It's amazing what kinds of problems are exposed
by folks that don't build compilers every day...
jeff
next prev parent reply other threads:[~1998-04-02 11:32 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 [this message]
1998-04-02 11:32 ` Joe Buck
1998-04-04 14:20 ` Jeffrey A Law
-- 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=1236.891365158@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).