From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] graphviz
Date: Thu, 4 Mar 2004 00:08:52 +0400 [thread overview]
Message-ID: <200403032008.i23K8qEd053150@adat.davidashen.net> (raw)
In-Reply-To: <1e613fb4c42ebe7817a54975b41da43b@plan9.ucalgary.ca>
>
> donate a hard drive to BL so they can put it on sources and create a
> /ports replica that we can all pull from.
This is doable.
> 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).
It will take longer, and does not make much sense for graphviz,
I am afraid.
next prev parent reply other threads:[~2004-03-03 20:08 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
2004-03-03 20:08 ` David Tolpin [this message]
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=200403032008.i23K8qEd053150@adat.davidashen.net \
--to=dvd@davidashen.net \
--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).