9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] vac flattens trees?
Date: Mon,  9 Mar 2009 11:11:16 -0400	[thread overview]
Message-ID: <ddb5e5af66899d634068e1c409190150@quanstro.net> (raw)
In-Reply-To: <df49a7370903090755p879ac84k1065d404cafafd43@mail.gmail.com>

> i suppose your preferred behaviour would be
> for it to do a treewise merge of the paths and
> vac the shallowest root that contains all the
> paths, missing out all contents that aren't
> under one of the named paths.
>
> this seems like quite an involved operation,
> when you can get much the same result
> by building a custom namespace containing the
> trees you want (admittedly, a recursive mntgen
> would be useful here).

wouldn't work on p9p.

it's hard to comment on the current behavior without
knowing the reasoning.  given your use case, it seems
like tar's model makes more sense.

a straightforward solution would be to have vac take
a proto.  i would think the -e flag would not scale.
then you can give a single root and include only the
stuff you want without changing current behavior.
and the bonus is that it works a lot like mkfs.

- erik



  reply	other threads:[~2009-03-09 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 13:35 Anthony Sorace
2009-03-09 14:55 ` roger peppe
2009-03-09 15:11   ` erik quanstrom [this message]
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=ddb5e5af66899d634068e1c409190150@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).