From: "Randy.Dunlap" <rddunlap@osdl.org>
To: gene.heskett@verizon.net
Cc: helgehaf@aitel.hist.no, zdzichu@irc.pl, linux-kernel@vger.kernel.org
Subject: Re: Large-FAT32-Filesystem Bug
Date: Mon, 8 Dec 2003 08:19:17 -0800 [thread overview]
Message-ID: <20031208081917.0a10b4db.rddunlap@osdl.org> (raw)
In-Reply-To: <200312080910.48676.gene.heskett@verizon.net>
On Mon, 8 Dec 2003 09:10:48 -0500 Gene Heskett <gene.heskett@verizon.net> wrote:
| On Monday 08 December 2003 04:54, Helge Hafting wrote:
| [...]
|
| >Digital cameras and such simply don't need long names.
| >
| >Helge Hafting
| >
| Humm, I'd argue that point, mine (Olympus C-3020) does a datestamp
| right in the filename, making it very easy to pick out the pix you
| shot while visiting someplace special. Thats at least as handy as
| sliced bread or bottled beer IMO.
but if it were important not to use long filenames, they could get
around this by using directories that contain the date info (only),
and files for that date inside each dir. E.g.,
20031201 <dir>
dscn0101.jpg
dscn0102.jpg
20031208 <dir>
dscn0103.jpg
dscn0104.jpg
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-12-08 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 9:52 Large-FAT32-Filesystem Bug Torsten Scheck
2003-12-05 13:17 ` jdow
2003-12-07 12:26 ` Helge Hafting
2003-12-07 12:20 ` Tomasz Torcz
2003-12-08 9:54 ` Helge Hafting
2003-12-08 14:10 ` Gene Heskett
2003-12-08 16:19 ` Randy.Dunlap [this message]
2003-12-07 13:56 ` Gene Heskett
2003-12-05 15:26 ` Eduard Bloch
2003-12-05 16:07 ` Erik Andersen
2003-12-05 17:54 ` Torsten Scheck
2003-12-05 22:10 ` Erik Andersen
2003-12-05 22:45 ` Mike Fedyk
2003-12-05 23:26 ` Måns Rullgård
2003-12-06 0:04 ` Andreas Schwab
2003-12-06 0:44 ` Måns Rullgård
2003-12-06 1:10 ` Andreas Schwab
2004-02-06 14:43 ` Torsten Scheck
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=20031208081917.0a10b4db.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=gene.heskett@verizon.net \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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).