From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] ls, rc question
Date: Fri, 19 Mar 2004 12:26:11 +0200 [thread overview]
Message-ID: <81132473206F3A46A72BD6116E1A06AE056171@black.aprote.com> (raw)
As Rob said, the current beahaviour is good in the sense that it's
simple and predictable. However, it would maybe also be nice to glob
match _names_, not paths. Right now, I fail to see, how it would
break something, e.g. acme.
next reply other threads:[~2004-03-19 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:26 Tiit Lankots [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-18 22:05 [9fans] ls question Russ Cox
2004-03-18 23:00 ` [9fans] ls, rc question David Tolpin
2004-03-19 3:41 ` rsc
2004-03-19 5:32 ` David Tolpin
2004-03-19 5:45 ` boyd, rounin
2004-03-19 5:50 ` ron minnich
2004-03-19 6:45 ` boyd, rounin
2004-03-19 9:07 ` Charles Forsyth
2004-03-19 9:24 ` Richard Miller
2004-03-19 9:33 ` boyd, rounin
2004-03-19 9:39 ` Richard Miller
2004-03-19 9:46 ` Geoff Collyer
2004-03-19 10:11 ` Richard Miller
2004-03-19 10:42 ` Charles Forsyth
2004-03-19 10:03 ` Charles Forsyth
2004-03-19 7:01 ` Micah Stetson
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=81132473206F3A46A72BD6116E1A06AE056171@black.aprote.com \
--to=t.lankots@aprote.ee \
--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).