From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 4194] Can't read directories with many files+directories
Date: Thu, 12 May 2022 05:31:08 +0000 [thread overview]
Message-ID: <bug-4194-10630-30mBqDOFTo@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-4194-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=4194
Björn Jacke <bjacke@samba.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|none |---
Product|Samba 3.0 |CifsVFS
QA Contact|samba-qa@samba.org |cifs-qa@samba.org
Version|3.0.23c |3.x
Component|Client Tools |kernel fs
--- Comment #6 from Björn Jacke <bjacke@samba.org> ---
moving to cifsvfs. I guess this is long fixed and should be closed, right?
--
You are receiving this mail because:
You are the QA Contact for the bug.
next parent reply other threads:[~2022-05-12 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-4194-10630@https.bugzilla.samba.org/>
2022-05-12 5:31 ` samba-bugs [this message]
2022-05-12 22:30 ` [Bug 4194] Can't read directories with many files+directories samba-bugs
2022-05-15 20:19 ` samba-bugs
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=bug-4194-10630-30mBqDOFTo@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox