From: hiro <23hiro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] question about #include_next directive
Date: Sat, 4 Aug 2018 00:55:30 +0200 [thread overview]
Message-ID: <CAFSF3XMx=yNSKqtT8-hLdTQmTqhv1MMEVS4p-MnH_iPBVCYzqg@mail.gmail.com> (raw)
In-Reply-To: <CAG2UyHrjxGs=G=Bz0bQ6csQoEYUG=RvvjGiLsfG68tedAX+ySg@mail.gmail.com>
don't mix work and play. this will end badly.
next prev parent reply other threads:[~2018-08-03 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 15:19 cinap_lenrek
2018-08-03 18:35 ` Kyohei Kadota
2018-08-03 18:54 ` Lyndon Nerenberg
2018-08-03 19:10 ` Dave MacFarlane
2018-08-03 22:55 ` hiro [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-03 14:35 Kyohei Kadota
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='CAFSF3XMx=yNSKqtT8-hLdTQmTqhv1MMEVS4p-MnH_iPBVCYzqg@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9fans@9fans.net \
/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).