From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil woe
Date: Wed, 7 Dec 2005 21:07:34 +0000 [thread overview]
Message-ID: <a98e350b9e30c4e018f3280837777593@quintile.net> (raw)
In-Reply-To: <44db37f075e341c3264601a498c2b4b7@vitanuova.com>
> why not make it possible to directly insert vac archives into
> a fossil filesystem?
I wanted to do this, I even got some hints from russ, but in
the end I failed - the pain/gain ratio of understanding that much
about fossil seemed too big.
It still sits on my to-do list though.
-Steve
next prev parent reply other threads:[~2005-12-07 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:02 Bruce Ellis
2005-12-06 22:07 ` Russ Cox
2005-12-06 22:19 ` Eric Van Hensbergen
2005-12-06 23:10 ` Bruce Ellis
2005-12-06 23:41 ` Russ Cox
2005-12-06 23:48 ` Bruce Ellis
2005-12-07 21:03 ` rog
2005-12-07 21:07 ` Steve Simon [this message]
2005-12-07 21:12 ` Bruce Ellis
2005-12-07 21:36 ` Russ Cox
2005-12-07 21:55 ` Bruce Ellis
2005-12-07 22:09 ` jmk
2005-12-07 22:41 ` Russ Cox
2005-12-07 21:49 ` jmk
2005-12-07 0:17 ` geoff
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=a98e350b9e30c4e018f3280837777593@quintile.net \
--to=steve@quintile.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).