[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Long filenames don't seem to work re: cp/touch (GNU fileutils) 3.16
From: |
Bob Proulx |
Subject: |
Re: Long filenames don't seem to work re: cp/touch (GNU fileutils) 3.16 |
Date: |
Sun, 8 Jul 2001 18:55:29 -0600 |
> The documentation states that the GNU FileUtils package handles long
> filenames. However, when I execute the following in a DOS box:
>
> cp a.txt "This is a long filename"
>
> The result is a file named "This is". I have also tried this with
> touch.exe and it too fails.
Thank you for your report. If you could make your report to the
Cygwin group it would be most appreciated. It looks like you are
hitting the 8 character file name with a 3 character extension DOS
limit.
Bob
Cygwin Home Page:
http://sources.redhat.com/cygwin/
Cygwin Bug Report Guidelines:
http://sources.redhat.com/cygwin/bugs.html
Where should I send bug reports?
First, you need to verify that your potential bug hasn't already
been reported by reading the Cygwin FAQ and the mailing list
archives. If your issue is still unresolved, feel free to write to
the cygwin list with your problem.
Please consider investigating it yourself and sending us patches if
you figure out a solution. Bug reports without solutions are also
welcome -- send a detailed description (with a test case if
possible) to the Cygwin mailing list after reading our bug reporting
guidelines. Due to the mailing list volume, we don't always reply to
individual bug reports sent to the list but we do keep track of
them.
Bug reporting guidelines
Use a subject line that describes the issue well:
Good examples:
"1.1.8: select bug (NT and 95)"
"1.1.6: problem building perl"
"1.1.8: question about catting binary files in bash"
Bad examples:
"bug"
"porting problem"
"help!!!!"
"bash question"
"newbie needs help"
This also applies to general discussion. It's very hard to
follow the list when most of the subject lines look very
similar.
In your description, show how to reproduce the problem. This
means including a test case if at all possible.
At the very least, always include which cygwin beta release you
are using and give the operating system and its version
number. E.g. "cygwin v1.1.9 under NT 4.0".
Run cygcheck -s -v -r > cygcheck.out and include that in your
report.
Keep in mind that there are over 1500 people on the mailing
list. Try to avoid "me too" responses or reporting problems
that have already been reported. It's hard enough keeping up
with the volume as it is...
Include a patch to fix the problem if you can. Please see how
to contribute for more information.