From: paurea@it.uc3m.es
To: 9fans@cse.psu.edu
Subject: Re: Re [9fans] union directories
Date: Thu, 22 Mar 2001 16:29:16 +0100 [thread overview]
Message-ID: <20010322152929.D66EA19A04@mail.cse.psu.edu> (raw)
>forsyth@caldo.demon.co.uk said:
>>bind -ac foo bar shoud give
>>*bar
>>foo
>>This is what I would expect intuitively. Of course you can always do ...
>i don't understand how this could be considered the `intuitive' interpret>ation.
The directory which is before for the lookup gets the creation. I
feel that is more consistent. If it is before, it is before for
everything...
Saludos,
Gorka
next reply other threads:[~2001-03-22 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 15:29 paurea [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 17:00 rob pike
2001-03-22 15:41 paurea
2001-03-22 15:36 Russ Cox
2001-03-22 4:47 forsyth
2001-03-22 3:28 Gorka Guardiola Muzquiz
2001-03-22 3:17 Gorka Guardiola Muzquiz
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=20010322152929.D66EA19A04@mail.cse.psu.edu \
--to=paurea@it.uc3m.es \
--cc=9fans@cse.psu.edu \
/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).