On Thu, Dec 23, 2004 at 10:10:49AM -0500, Christopher Faylor wrote:
>If you don't see it in CVS, then it is still being worked on and asking
>people for a work in progress and you don't want a work in progress.
Oops.
"If you see it in CVS, then it is still being worked on and you don't
want a wor
On Thu, Dec 23, 2004 at 08:04:45AM -0700, Mark Paulus wrote:
>On Thu, 23 Dec 2004 11:35:40 +0100, Corinna Vinschen wrote:
>
>
>>While you're right, it's not a good thing that ls // returns these
>>error messages. I found a buglet in Cygwin which results in scanning
>>the root directory accidentall
On Thu, 23 Dec 2004 11:35:40 +0100, Corinna Vinschen wrote:
>While you're right, it's not a good thing that ls // returns these
>error messages. I found a buglet in Cygwin which results in scanning
>the root directory accidentally in this situation.
For us non-informed, commercial developers,
On Dec 22 15:47, Andrew DeFaria wrote:
> Mark Paulus wrote:
>
> >When I do an ls -F, I get expected results:
> >$ ls -F /
> >bin/ cygwin.bat* home/ run.groff tmp1/ xfer/
> >cron_diagnose.sh* cygwin.ico* lib/ sbin/ usr/
> >cygdeb/ etc/ mountem* tmp/ var/
> >
> >However, when I do ls -F //, then I g
Mark Paulus wrote:
When I do an ls -F, I get expected results:
$ ls -F /
bin/ cygwin.bat* home/ run.groff tmp1/ xfer/
cron_diagnose.sh* cygwin.ico* lib/ sbin/ usr/
cygdeb/ etc/ mountem* tmp/ var/
However, when I do ls -F //, then I get bad results:
$ ls -F //
ls: //bin: No such file or directory
ls
When I do an ls -F, I get expected results:
$ ls -F /
bin/ cygwin.bat* home/ run.groff tmp1/ xfer/
cron_diagnose.sh* cygwin.ico* lib/ sbin/ usr/
cygdeb/etc/ mountem* tmp/ var/
However, when I do ls -F //, then I get bad results:
$ ls -F /
6 matches
Mail list logo