From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] vac flattens trees?
Date: Mon, 9 Mar 2009 23:39:50 -0400 [thread overview]
Message-ID: <d7621e00dcbe4165277dc1dd41e0795e@quanstro.net> (raw)
In-Reply-To: <509071940903092029r56612290hcfa33dc434eacfa8@mail.gmail.com>
On Mon Mar 9 23:30:22 EDT 2009, anothy@gmail.com wrote:
> that seems a little awkward. erik's suggestion is what i
> think i'd really like. rog's would be okay, although still
> somewhatawkward, were i on plan 9; since i'm not, i think
> i have russ's option. so with -x, say i had a tree:
>
> /dog
> /cat
> /fish/guppie
> /fish/clown
> /pig
>
> and i wanted /dog, /cat, and /fish/clown. would three
> includes be sufficent there, or do i need it include /fish and
> then exclude /fish/guppie, to get the heirarchy?
>
> i do wish more tools used proto. the format is so nice.
oh, you already know what i'm going to suggest, so
just get to it!
russ: i don't think in understand your motivating case. if
you want to flatten /some/long/path/target to just target,
why can't you just cd there? there must be some other part
i haven't gotten yet.
- erik
next prev parent reply other threads:[~2009-03-10 3:39 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
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 [this message]
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=d7621e00dcbe4165277dc1dd41e0795e@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).