From: Mircea Ciocan <mirceac@interplus.ro>
To: Linux-kernel@vger.kernel.org
Subject: Can I have my loop FS back, plizzz !!!
Date: Sun, 18 Feb 2001 11:48:30 +0200 [thread overview]
Message-ID: <3A8F9A6E.E44261AF@interplus.ro> (raw)
2.4.1ac18 and loop-4 doesn't mix at all well, it didn't even compile (
understandably (sp?) if we think that a large hunk of loop.c is
rejected, and by studing the reject it seem to me that the original
version and loop-4 are going in differend directions :( ).
So, lacking the skills to fix-it myself I'll try a new INNOVATIVE
approach: "Begging the Developers (TM:)" that was reported to give
excelent results in the past:
" Can I have my lil'ol loop FS back, plizzzz, plizzzz, I need it badly
but also I need the other improvements in ac18, I know you are busy with
other important things, but pleeez ( innocent look :)"
And it remains to see if once again this method gives results ;)))).
Mircea "too many bad loops" C.
reply other threads:[~2001-02-18 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A8F9A6E.E44261AF@interplus.ro \
--to=mirceac@interplus.ro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox