From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] graphviz
Date: Wed, 3 Mar 2004 12:59:50 -0700 [thread overview]
Message-ID: <1e613fb4c42ebe7817a54975b41da43b@plan9.ucalgary.ca> (raw)
In-Reply-To: <200403031945.i23JjVpk053049@adat.davidashen.net>
> What is the accepted way to deliver ports?
donate a hard drive to BL so they can put it on sources and create a
/ports replica that we can all pull from.
make sure it's all mkfiles and doesn't require ape/psh to be run just
to get 'make' going (rewriting makefiles into mkfiles is an exercise
in how things can be done right in one OS and wrong in another).
andrey
next prev parent reply other threads:[~2004-03-03 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 19:45 David Tolpin
2004-03-03 19:59 ` andrey mirtchovski [this message]
2004-03-03 20:08 ` David Tolpin
2004-03-03 20:15 ` andrey mirtchovski
2004-03-03 20:22 ` David Tolpin
2004-03-03 21:00 ` splite
2004-03-03 21:08 ` David Tolpin
2004-03-03 21:42 ` splite
2004-03-04 9:59 ` Robin KAY
2004-03-03 22:29 ` boyd, rounin
2007-06-11 6:43 [9fans] Graphviz Lyndon Nerenberg
2007-06-11 7:02 ` Gabriel Diaz
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=1e613fb4c42ebe7817a54975b41da43b@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).