From: C H Forsyth <forsyth@vitanuova.com>
To: leimy2k@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] Patch updates and changes
Date: Tue, 27 Sep 2005 09:34:38 +0100 [thread overview]
Message-ID: <1bbc0522424d511b4b63704f88292cd7@vitanuova.com> (raw)
In-Reply-To: <3e1162e6050926115666f71490@mail.gmail.com>
>>The error message was "bad name" and the man
>>page didn't mention that capitals were disallowed either.
having looked at the script, i suspect the main intention was
to eliminate characters strange enough that it would be `obvious'
why the name was bad (#&@!?*) but of course since the grep pattern
doesn't include upper case, you get a diagnostic that makes less sense.
usually none of the rest of us can find the shift key,
so i for one had never noticed!
prev parent reply other threads:[~2005-09-27 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 21:11 Uriel
2005-09-26 18:56 ` David Leimbach
2005-09-27 8:34 ` C H Forsyth [this message]
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=1bbc0522424d511b4b63704f88292cd7@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
--cc=leimy2k@gmail.com \
/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).