From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] [kenfs] the mercurial repo problem
Date: Thu, 2 Feb 2012 07:49:47 -0500 [thread overview]
Message-ID: <2fff508f351d00f8bb91a2eb4eb14a60@coraid.com> (raw)
In-Reply-To: <CABwSpPAuOy_MYf1ewJY92L0BK0DuLBv99HYnFU+nHV25n5w5vg@mail.gmail.c>
On Thu Feb 2 06:57:40 EST 2012, akumar@mail.nanosouffle.net wrote:
> This is a problem perhaps two of us
> have on Plan 9 (hi Erik): mercurial
> repositories contain files with long
> names and/or spaces.
coraid run's ken's file server. so a fair percentage
of plan 9 users run on that rather than fossil.
- erik
next parent reply other threads:[~2012-02-02 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABwSpPAuOy_MYf1ewJY92L0BK0DuLBv99HYnFU+nHV25n5w5vg@mail.gmail.c>
2012-02-02 12:49 ` erik quanstrom [this message]
2012-02-02 11:56 Akshat Kumar
2012-02-02 12:05 ` Akshat Kumar
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=2fff508f351d00f8bb91a2eb4eb14a60@coraid.com \
--to=quanstro@labs.coraid.com \
--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).