9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] frogs and osx
Date: Fri,  4 Jan 2008 20:52:37 +1100	[thread overview]
Message-ID: <775b8d190801040152n1a239619x7dcdf31796fd181e@mail.gmail.com> (raw)
In-Reply-To: <0056CF0F-5431-456B-89E4-C379EB281ABB@orthanc.ca>

NO! a frog is a mistake. '\n' and '\r' are both frogs so where did
you get the EOL thing from.  i want neither in my filenames.
if you do then change your copy of the code.  or make up a new
reason not to.  make your own island of tranquility.

brucee

On Jan 4, 2008 6:45 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>
> On 2008-Jan-4, at 00:31 , Bruce Ellis wrote:
>
> > not at all, pragmatic.excluding crap from filenames was and still is
> > good.
> > if you want to vote '\r' as "not a mistake"  you can.  but filenames
> > created
> > from buggy stuff die dead, as they should.
>
> We are arguing different things. EOL conventions are religion.  Kernel
> delimiters are just code.
>


  reply	other threads:[~2008-01-04  9:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 19:46 Steve Simon
2008-01-04  2:29 ` Russ Cox
2008-01-04  6:35   ` Bruce Ellis
2008-01-04  7:24   ` Lyndon Nerenberg
2008-01-04  7:31     ` Bruce Ellis
2008-01-04  7:37       ` Lyndon Nerenberg
2008-01-04  7:45         ` Bruce Ellis
2008-01-04  7:45       ` Lyndon Nerenberg
2008-01-04  9:52         ` Bruce Ellis [this message]
2008-01-04 10:17           ` Steve Simon
2008-01-04 10:26             ` Bruce Ellis
2008-01-04 11:22     ` Pietro Gagliardi
2008-02-06 13:51       ` underspecified

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=775b8d190801040152n1a239619x7dcdf31796fd181e@mail.gmail.com \
    --to=bruce.ellis@gmail.com \
    --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).