From: <cej@gli.cas.cz>
To: <9fans@9fans.net>
Subject: Re: [9fans] troff bibliography
Date: Wed, 10 Dec 2008 08:06:26 +0100 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17DD660A9@XMAIL.asuch.cas.cz> (raw)
In-Reply-To: <4B026100-F3B3-44F0-83EB-6B9E020EAADF@mac.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
yep. i'll try just refer&allies, and we'll see. looks like it wouldn't make much problem, namely if i follow the style forsyth did the ape port...
thanks, regards,
peter, aka ++pac.
>This is probably because the Heirloom tools are different from the
>Plan 9 tools. I think you should try compiling the Heirloom tools
>using ape/psh and see what happens.
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2635 bytes --]
next prev parent reply other threads:[~2008-12-10 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 11:23 cej
2008-12-09 11:33 ` Pietro Gagliardi
2008-12-09 11:36 ` cej
2008-12-09 11:41 ` cej
2008-12-09 22:58 ` Pietro Gagliardi
2008-12-10 7:06 ` cej [this message]
2008-12-11 13:13 ` cej
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=ACCF003CBA3D09458207DB0CB86AD17DD660A9@XMAIL.asuch.cas.cz \
--to=cej@gli.cas.cz \
--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).