From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] import/export -B
Date: Mon, 25 Oct 2010 09:48:03 -0400 [thread overview]
Message-ID: <302f38636b6c2ec3dbf5e6fba857f3ab@ladd.quanstro.net> (raw)
In-Reply-To: <c2fcd790e1ba2a621584dba594b8d0ea@quintile.net>
> The only bit I don't get is why you have to supply a mountpoint to import.
> Surely import will always be running from listen and as such it will not
> be in any useful namespace so why mount anything?
would it make more sense if it instead said "root of tree to be mounted"?
- erik
prev parent reply other threads:[~2010-10-25 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 12:01 Steve Simon
2010-10-25 13:48 ` erik quanstrom [this message]
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=302f38636b6c2ec3dbf5e6fba857f3ab@ladd.quanstro.net \
--to=quanstro@quanstro.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).