From: Philipp Thomas <pthomas@suse.de>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: cp/errfn.c
Date: Fri, 07 Jul 2000 05:53:00 -0000 [thread overview]
Message-ID: <20000707145254.F2335@Jeffreys.suse.de> (raw)
In-Reply-To: <20000706223425Q.mitchell@codesourcery.com>
* Mark Mitchell (mark@codesourcery.com) [20000707 07:34]:
> And errfns.c is code that is likely to end up more widely shared than it
> presently is.
>
> Does that make sense?
Yes, it does. Thanks for the explanation.
Philipp
--
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany
#define NINODE 50 /* number of in core inodes */
#define NPROC 30 /* max number of processes */
-- Version 7 UNIX for PDP 11, /usr/include/sys/param.h
next prev parent reply other threads:[~2000-07-07 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 21:06 cp/errfn.c Philipp Thomas
2000-07-06 22:34 ` cp/errfn.c Mark Mitchell
2000-07-07 5:53 ` Philipp Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-02 19:07 cp/errfn.c Mike Stump
1998-02-02 15:13 cp/errfn.c John Carr
1998-02-06 0:57 ` cp/errfn.c Jeffrey A Law
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=20000707145254.F2335@Jeffreys.suse.de \
--to=pthomas@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).