From: V13 <v13@priest.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Tomas Szepe <szepe@pinerecords.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
dsaxena@plexity.net, greg@kroah.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] Remove spaces from PCI IDE pci_driver.name field
Date: Tue, 10 Aug 2004 19:52:17 +0300 [thread overview]
Message-ID: <200408101952.18710.v13@priest.com> (raw)
In-Reply-To: <1092154407.10794.14.camel@mindpipe>
On Tuesday 10 August 2004 19:13, Lee Revell wrote:
> On Tue, 2004-08-10 at 11:57, Tomas Szepe wrote:
> > Sure, but while with a GUI you can click on almost anything, on the
> > command line spaces in filenames have always been a real pain in
> > the ass, so let's not pretend otherwise.
>
> Ever heard of tab completion? Think of it as click for the command
> line.
>
> Seriously, do you really *prefer* filenames like
> Foo_Bar-Baa_Baaz_Quux.mp3?
Anyone that writes scripts prefers filenames without spaces. It simplifies
scripts *and* typing a lot.
Card\ 01
Card\ 02
Cardinal
Now we have to write: cd Ca<tab>\ <tab>1<tab/space>
On the other hand, perhaps /sys should be named 'My computer' :P
> Lee
<<V13>>
p.s. I believe upper-lower case is a similar (or worst) 'problem' too,
regarding typing.
next prev parent reply other threads:[~2004-08-10 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 0:13 [PATCH 2.6] Remove spaces from PCI IDE pci_driver.name field Deepak Saxena
2004-08-10 0:11 ` Alan Cox
2004-08-10 2:12 ` Deepak Saxena
2004-08-10 11:52 ` Alan Cox
2004-08-10 15:57 ` Tomas Szepe
2004-08-10 16:13 ` Lee Revell
2004-08-10 16:18 ` Tomas Szepe
2004-08-10 16:52 ` V13 [this message]
2004-08-10 16:55 ` Lee Revell
2004-08-10 16:57 ` Tomas Szepe
2004-08-10 17:00 ` Lee Revell
2004-08-10 16:40 ` Greg KH
2004-08-10 23:41 ` Greg KH
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=200408101952.18710.v13@priest.com \
--to=v13@priest.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dsaxena@plexity.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=szepe@pinerecords.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.