From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ftpfs & fmtinstall woe
Date: Wed, 25 May 2005 14:41:15 +0100 [thread overview]
Message-ID: <4d0a5dab121be47e2ac88fd30616be4d@vitanuova.com> (raw)
In-Reply-To: <695de14f1982116d93904ae698bac35f@terzarima.net>
bitten by this in the past, i wondered if there was a good
reason why -F was separate from -w. are there many times when
you want warnings but want the compiler to ignore the varargs
pragmas?
next prev parent reply other threads:[~2005-05-25 13:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 1:19 boyd, rounin
2005-05-22 1:52 ` Russ Cox
2005-05-22 2:11 ` boyd, rounin
2005-05-22 2:48 ` Russ Cox
2005-05-22 2:57 ` boyd, rounin
2005-05-22 4:06 ` jmk
2005-05-22 4:15 ` boyd, rounin
2005-05-22 4:24 ` jmk
2005-05-22 4:36 ` boyd, rounin
2005-05-22 4:42 ` jmk
2005-05-22 4:32 ` Russ Cox
2005-05-22 4:43 ` boyd, rounin
2005-05-22 4:57 ` Russ Cox
2005-05-22 7:35 ` Bruce Ellis
2005-05-22 7:38 ` Skip Tavakkolian
2005-05-22 7:41 ` Bruce Ellis
2005-05-22 7:45 ` Skip Tavakkolian
2005-05-22 7:46 ` Skip Tavakkolian
2005-05-22 7:50 ` Bruce Ellis
2005-05-23 3:40 ` Ronald G. Minnich
2005-05-22 7:51 ` Charles Forsyth
2005-05-22 7:56 ` Bruce Ellis
2005-05-25 13:41 ` rog [this message]
2005-05-25 16:14 ` Bruce Ellis
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=4d0a5dab121be47e2ac88fd30616be4d@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).