From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] allow to create a minix3fs with a blocksize != 1K
Date: Thu, 10 May 2012 00:04:09 +0200 [thread overview]
Message-ID: <4FAAE9D9.40707@gmail.com> (raw)
In-Reply-To: <CAFLxGvzo9JNGdxGqr1nn+aQtq7aiVOqkn+bD7Xn7idvfKo-wrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On 09.05.2012 23:57, richard -rw- weinberger wrote:
> On Wed, May 9, 2012 at 11:51 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>> Have used it to test minixfs support with various block sizes.
>>
> Isn't this patch against disk-utils?
> Why are you sending it to linux-kernel@..?
Yes, I've already noticed this and resent it to the util-linux list.
Do you know if linux-kernel is the right list for my other patches like
wrong minixfs block allocation check or AFFS race condition? It seems
they've all been ignored.
I have few other bugfixes or feature improvements for lesser filesystems
but I don't want to send them unless I feel like the patches are going
to somewhere else than /dev/null.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2012-05-09 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 21:51 [PATCH] allow to create a minix3fs with a blocksize != 1K Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-09 21:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-15 9:05 ` Karel Zak
2012-06-10 19:58 ` Davidlohr Bueso
2012-06-10 20:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-06-11 11:45 ` Davidlohr Bueso
2012-05-09 21:57 ` richard -rw- weinberger
2012-05-09 22:04 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-05-09 22:08 ` richard -rw- weinberger
2012-05-09 22:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4FAAE9D9.40707@gmail.com \
--to=phcoder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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.