From: Wayne.Brown@altec.com
To: linux-kernel@vger.kernel.org
Subject: Re: strange directory problem
Date: Fri, 15 Dec 2000 16:25:59 -0600 [thread overview]
Message-ID: <862569B6.007B3A89.00@smtpnotes.altec.com> (raw)
Is anyone besides me getting multiple copies of Jeff Epler's message? I've
gotten at least a couple of dozen copies of this (and another long message by
Ted T'so with the subject "Re: Serial cardbus code.... for testing, please.....
") since yesterday. They arrive once or twice an hour, all day long. Obviously
there's a loop somewhere, but only these two messages seem to be affected. If
no one else is seeing the duplicates I'll have our local mail admistrators look
at it, but I hate to accuse their software of being the problem without some
indication that it's only happening locally.
Wayne
Jeff Epler <jepler@inetnebr.com> on 12/13/2000 09:25:33 AM
To: linux-kernel@vger.kernel.org
cc: (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: strange directory problem
On Wed, Dec 13, 2000 at 02:13:51PM +0100, Gabor Lenart wrote:
> Hi,
>
> lgb@vega:~$ uname -a
> Linux vega 2.2.18pre24 #1 Thu Dec 7 14:08:36 CET 2000 i686 unknown
>
> I created a directory from shell (bash). The next ls didn't show it,
> I had to type ls second time too to get the changes. Is it a known bug?
> Is it fixed in 2.2.18final ?
NFS, or a local filesystem?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-15 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 22:25 Wayne.Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-13 13:13 strange directory problem Gabor Lenart
2000-12-13 15:25 ` Jeff Epler
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=862569B6.007B3A89.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=linux-kernel@vger.kernel.org \
/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.