From: "Виталий Филиппов" <vitalif@yourcmc.ru>
To: "Andreas Dilger" <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org
Subject: Re: A tool that allows changing inode table sizes
Date: Sun, 22 Jan 2017 12:05:27 +0300 [thread overview]
Message-ID: <op.yugl7dquvqcmy1@gnusmas> (raw)
In-Reply-To: <E615B1F7-70D9-4342-97BE-6ADB83BF9589@yourcmc.ru>
Hi again,
I've got no answer since this email...
But I still would like to have my patch merged. What should I do now?
> Ok, thank you :-)
>
> 28 сентября 2016 г. 20:37:37 GMT+03:00, Andreas Dilger
> <adilger@dilger.ca> пишет:
>> On Sep 28, 2016, at 10:00 AM, Виталий Филиппов <vitalif@yourcmc.ru>
>> wrote:
>>> Thanks, did you see that email? Or was it lost somewhere in between?
>>
>> I did, but just didn't reply since resize2fs and bigalloc are Ted's
>> area.
>> He is often travelling, so it may take some time for him to reply.
>>
>> Cheers, Andreas
>>
>>> 28 сентября 2016 г. 17:46:52 GMT+03:00, Andreas Dilger
>> <adilger@dilger.ca> пишет:
>>> On Sep 28, 2016, at 6:14 AM, vitalif@yourcmc.ru wrote:
>>> Hi!
>>> I want to send a patch for e2fsprogs - I've implemented inode table
>> resizing in resize2fs.
>>> To what mailing list should I send it?
>>> I've written something to linux-ext4, but got no answer...
>>> linux-ext4 is the right list.
>>> Cheers, Andreas
next prev parent reply other threads:[~2017-01-22 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 13:28 A tool that allows changing inode table sizes vitalif
2014-01-17 0:05 ` Andreas Dilger
2014-01-17 0:25 ` Darrick J. Wong
2016-09-25 21:23 ` Виталий Филиппов
2016-09-28 12:14 ` vitalif
2016-09-28 14:46 ` Andreas Dilger
[not found] ` <9156EEF4-B49F-4ADD-9C62-1E70FC18395C@yourcmc.ru>
[not found] ` <E1C44EA0-0C53-46AF-8CC1-DE7A44986CAA@dilger.ca>
[not found] ` <E615B1F7-70D9-4342-97BE-6ADB83BF9589@yourcmc.ru>
2017-01-22 9:05 ` Виталий Филиппов [this message]
2014-01-17 13:21 ` vitalif
2014-02-27 16:35 ` Phillip Susi
2014-02-27 21:12 ` Vitaliy Filippov
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=op.yugl7dquvqcmy1@gnusmas \
--to=vitalif@yourcmc.ru \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).