From: "David A. Deal" <ddeal@orincon.com>
To: <egcs@egcs.cygnus.com>
Subject: Successful Build
Date: Thu, 06 May 1999 13:22:00 -0000 [thread overview]
Message-ID: <000901be97fe$76748e30$1a55d3c6@orincon.com> (raw)
I noticed my build wasn't _exactly_ listed on your 'build status page':
dt030nd5:ddeal=>uname -a
Linux dt030nd5 2.0.36 #1 Tue Oct 13 22:17:11 EDT 1998 i686 unknown
dt030nd5:ddeal=>../config.guess
i686-pc-linux-gnu
David A. Deal
Software Engineer
Orincon Corporation
9363 Towne Centre Drive
San Diego, CA 92121-3017
ddeal@orincon.com
619-455-5530 ex. 306
WARNING: multiple messages have this Message-ID
From: "David A. Deal" <ddeal@orincon.com>
To: <egcs@egcs.cygnus.com>
Subject: Successful Build
Date: Mon, 31 May 1999 21:36:00 -0000 [thread overview]
Message-ID: <000901be97fe$76748e30$1a55d3c6@orincon.com> (raw)
Message-ID: <19990531213600.9agyDjL8NfEzgfhs5TGwV9slJmDE7JKMj9KC7RbUAfQ@z> (raw)
I noticed my build wasn't _exactly_ listed on your 'build status page':
dt030nd5:ddeal=>uname -a
Linux dt030nd5 2.0.36 #1 Tue Oct 13 22:17:11 EDT 1998 i686 unknown
dt030nd5:ddeal=>../config.guess
i686-pc-linux-gnu
David A. Deal
Software Engineer
Orincon Corporation
9363 Towne Centre Drive
San Diego, CA 92121-3017
ddeal@orincon.com
619-455-5530 ex. 306
next reply other threads:[~1999-05-06 13:22 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-06 13:22 David A. Deal [this message]
1999-05-31 21:36 ` David A. Deal
-- strict thread matches above, loose matches on Subject: below --
2010-06-08 15:27 Successful build Maynard, William L. (GSFC-5540)
2008-03-15 4:10 successful build Christian Schüler
2007-12-24 7:53 Successful Build Aran Clauson
2006-02-03 10:12 Dinosaur
2006-01-31 22:43 Dinosaur
2003-07-01 15:06 Successful build Dan Schult
2003-07-01 15:12 ` Andrew Pinski
2003-03-11 20:15 Willard Myers
2003-02-13 21:38 'David Scott Urban
2002-11-26 6:33 successful build Alexander Darovsky
2002-09-03 15:27 Successful build Miguel Bazdresch
2002-09-03 16:08 ` Janis Johnson
2002-08-26 6:35 successful build John Griessen
2002-08-26 16:36 ` Janis Johnson
2002-05-16 12:22 Daniel Wesslén
2002-05-16 12:15 Marek Tilk Materzok
2002-05-16 13:16 ` Florian Weimer
2002-05-16 17:35 ` Janis Johnson
2002-04-09 1:55 Successful Build Bob
2002-03-14 14:20 Don Allen
2002-03-14 16:36 ` Janis Johnson
2002-01-20 11:37 successful build Kevin Franden
2002-01-21 9:37 ` Janis Johnson
2001-12-16 17:52 Juan Jose Martin
2001-12-17 9:15 ` Janis Johnson
2001-12-07 16:00 Successful Build platter
2001-12-11 16:20 ` Janis Johnson
2001-10-30 7:56 Successful build Marc Soda
2001-10-30 8:48 ` Janis Johnson
2001-10-03 17:07 successful build Matt Kraai
2001-10-04 10:44 ` Janis Johnson
2001-09-23 10:02 Successful build John Warriner
2001-09-24 11:26 ` Janis Johnson
2001-09-24 11:32 ` Jack Cummings
2001-09-24 11:45 ` Janis Johnson
2001-09-24 11:55 ` Jack Cummings
2001-09-24 16:47 ` Janis Johnson
2001-09-24 16:51 ` Jack Cummings
2001-09-25 10:17 ` Janis Johnson
2001-09-14 3:23 Bert De Knuydt
2001-09-14 9:41 ` Janis Johnson
2001-08-01 6:15 successful build Amy
1999-08-02 5:49 David J. Dooling
1999-08-31 23:20 ` David J. Dooling
1999-07-31 12:41 David J. Dooling
1999-07-31 23:33 ` David J. Dooling
1998-11-21 7:09 Successful build aaron schmiedel 214.924.8225
1998-09-06 15:12 successful build David Long
1998-08-25 19:31 Successful build furio ercolessi
1998-06-19 23:47 J Scott Berg
1998-06-16 5:45 Christopher Minekime
1998-02-06 6:19 Michael Remski
1997-12-05 6:20 Lars Hecking
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='000901be97fe$76748e30$1a55d3c6@orincon.com' \
--to=ddeal@orincon.com \
--cc=egcs@egcs.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).