From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [kenfs] the mercurial repo problem
Date: Thu, 2 Feb 2012 04:05:57 -0800 [thread overview]
Message-ID: <CABwSpPBM2Z-tpHucZH=QAXdWdugwa+w5NTEhcngQtVNswZQswg@mail.gmail.com> (raw)
In-Reply-To: <CABwSpPAuOy_MYf1ewJY92L0BK0DuLBv99HYnFU+nHV25n5w5vg@mail.gmail.com>
Ah, sorry to double-post, but in order
to get this working, one must:
mkdir repo
hg init repo
cd repo; hg pull -u https://...
echo '[paths]
default = https://...' > .hg/hgrc
Because it is forbidden to directly
clone on a non-empty directory
(an lnfs mounted dir contains a
.longnames index file).
ak
On Thu, Feb 2, 2012 at 3:56 AM, Akshat Kumar
<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.
>
> I realised that `lnfs' is a neat solution
> to this problem (though you have to
> remember to run it each time you're
> in the repo) for the time-being. In
> particular, it doesn't hog up ram (the
> way ramfs does... :), and it doesn't
> rely on the repo .hg dir already being
> there (the way hgfs does), which is
> what usually contains the long names.
> And we can use `unlnfs' to export.
>
> Just for future reference -- I noticed that
> this didn't come up when we last discussed
> this issue.
>
> As always -
>
> BUGS
> This exists only to shame us into getting a real long name
> file server working.
> (Yeah, yeah - fossilheads can SUCK EGGS :-)
>
>
> Best,
> ak
next prev parent reply other threads:[~2012-02-02 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 11:56 Akshat Kumar
2012-02-02 12:05 ` Akshat Kumar [this message]
[not found] <CABwSpPAuOy_MYf1ewJY92L0BK0DuLBv99HYnFU+nHV25n5w5vg@mail.gmail.c>
2012-02-02 12:49 ` erik quanstrom
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='CABwSpPBM2Z-tpHucZH=QAXdWdugwa+w5NTEhcngQtVNswZQswg@mail.gmail.com' \
--to=akumar@mail.nanosouffle.net \
--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).