From: "Benjamin C. Pierce" <bcpierce@saul.cis.upenn.edu>
To: unison-users@egroups.com, unison-announce@egroups.com,
caml-list@inria.fr
Subject: [Caml-list] Calling all power Unison users...
Date: Thu, 15 Nov 2001 08:18:14 EST [thread overview]
Message-ID: <14652.1005830294@saul.cis.upenn.edu> (raw)
We are finishing up a paper on the design and implementation of Unison
(to be submitted to Usenix), and we'd like to include some discussion of
the kinds of things that people are using it for.
If you consider yourself a "power user" -- i.e., you regularly
synchronize more than a couple of gigabytes, use it to administer a
system for more than just yourself, etc., could you drop me a quick note
saying what you're doing?
Thanks,
-- B
P.S. I'll summarize the results to the unison-users list
(http://groups.yahoo.com/group/unison-users), in case other people are
curious.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
reply other threads:[~2001-11-15 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14652.1005830294@saul.cis.upenn.edu \
--to=bcpierce@saul.cis.upenn.edu \
--cc=bcpierce@cis.upenn.edu \
--cc=caml-list@inria.fr \
--cc=unison-announce@egroups.com \
--cc=unison-users@egroups.com \
/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