From: Anthony Sorace <anothy@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] vac flattens trees?
Date: Mon, 9 Mar 2009 09:35:49 -0400 [thread overview]
Message-ID: <509071940903090635l48dcaccfu99c4d9e269e4ec0f@mail.gmail.com> (raw)
given a list of files like "/fish /dog /snake/asp /snake/python", the
results of a vac (as interpreted by vacfs) seem to be "/fish /dog /asp
/python". is this intentional? it seems unexpected, and makes doing
selective backups using vac a bit awkward.
this is vac on p9p and vacfs on plan9, if that matters.
next reply other threads:[~2009-03-09 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 13:35 Anthony Sorace [this message]
2009-03-09 14:55 ` roger peppe
2009-03-09 15:11 ` erik quanstrom
2009-03-09 16:08 ` Russ Cox
2009-03-09 16:43 ` roger peppe
2009-03-09 19:01 ` Russ Cox
2009-03-09 19:11 ` roger peppe
2009-03-09 19:34 ` Jeff Sickel
2009-03-09 20:55 ` Latchesar Ionkov
2009-03-10 3:29 ` Anthony Sorace
2009-03-10 3:39 ` erik quanstrom
2009-03-10 3:53 ` john
2009-03-10 3:55 ` erik quanstrom
2009-03-10 3:43 ` Russ Cox
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=509071940903090635l48dcaccfu99c4d9e269e4ec0f@mail.gmail.com \
--to=anothy@gmail.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).