From: Mark Alexander <marka@cygnus.com>
To: gdb-patches@cygnus.com, robert.hoehne@gmx.net
Cc: dj@delorie.com
Subject: Re: Filename change to fit the "only one dot" limitation on DOS
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990314153048.B1050@cygnus.com> (raw)
In-Reply-To: <199903142314.PAA09806@andros.cygnus.com>
On Sun, Mar 14, 1999 at 03:14:24PM -0800, Stan Shebs wrote:
> Just out of curiosity,
> why isn't it a problem that the generated filenames are longer than 8 chars?
DOS allows long names; it silently truncates everything after 8.3.
What's left of the filename after this truncation has to be unique and
not have "illegal" characters.
WARNING: multiple messages have this Message-ID
From: Mark Alexander <marka@cygnus.com>
To: gdb-patches@cygnus.com, robert.hoehne@gmx.net
Cc: dj@delorie.com
Subject: Re: Filename change to fit the "only one dot" limitation on DOS
Date: Sun, 14 Mar 1999 15:31:00 -0000 [thread overview]
Message-ID: <19990314153048.B1050@cygnus.com> (raw)
Message-ID: <19990314153100.z4haxqs8d8g5oH8vrUMsyiGbf8EpkPaNlduPdgMGhZA@z> (raw)
In-Reply-To: <199903142314.PAA09806@andros.cygnus.com>
On Sun, Mar 14, 1999 at 03:14:24PM -0800, Stan Shebs wrote:
> Just out of curiosity,
> why isn't it a problem that the generated filenames are longer than 8 chars?
DOS allows long names; it silently truncates everything after 8.3.
What's left of the filename after this truncation has to be unique and
not have "illegal" characters.
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 Robert Hoehne
1999-03-14 14:41 ` Robert Hoehne
1999-03-14 15:14 ` Stan Shebs
1999-04-01 0:00 ` DJ Delorie
1999-03-14 15:25 ` DJ Delorie
1999-04-01 0:00 ` Mark Alexander [this message]
1999-03-14 15:31 ` Mark Alexander
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Andrew Cagney
1999-03-14 16:08 ` Andrew Cagney
1999-04-01 0:00 ` Stan Shebs
1999-03-14 17:30 ` Stan Shebs
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=19990314153048.B1050@cygnus.com \
--to=marka@cygnus.com \
--cc=dj@delorie.com \
--cc=gdb-patches@cygnus.com \
--cc=robert.hoehne@gmx.net \
/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