From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Corentin Chary <corentincj@iksaif.net>,
linux-mtd@lists.infradead.org, vapier.adi@gmail.com
Subject: Re: [PATCH 0/3] libubi / mkfs.ubifs #2
Date: Mon, 11 May 2009 10:19:50 +0300 [thread overview]
Message-ID: <1242026390.27996.132.camel@localhost.localdomain> (raw)
In-Reply-To: <71cd59b00905110002j57b57767s2f25132b381876d4@mail.gmail.com>
On Mon, 2009-05-11 at 09:02 +0200, Corentin Chary wrote:
> On Sat, May 9, 2009 at 11:41 AM, Corentin Chary <corentincj@iksaif.net> wrote:
> > These patchs will allow mkfs.ubifs to write the image directly
>
> Again, there are waiting for moderator approval because they have a
> suspicious header :/
> Can be caused by
> X-Bad-Reply: References and In-Reply-To but no 'Re:' in Subject.
> but I'm not sure.
> I send them with git, maybe next time I won't send them as a thread ?
> thanks
This is broken MTD ML filter. Patch series are incorrectly caught.
Few years ago dwmw2 was going to fix this :-)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-11 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 9:41 [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-09 9:41 ` [PATCH 1/3] libubi: add ubi_is_mapped() function Corentin Chary
2009-05-09 9:41 ` [PATCH 2/3] libubi: fix multiple memory corruptions Corentin Chary
2009-05-09 9:41 ` [PATCH 3/3] mkfs.ubifs: use libubi to format UBI volume Corentin Chary
2009-05-13 8:12 ` Artem Bityutskiy
2009-05-13 8:38 ` Corentin Chary
2009-05-13 8:46 ` Artem Bityutskiy
2009-05-11 7:02 ` [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-11 7:19 ` Artem Bityutskiy [this message]
2009-05-11 7:21 ` Artem Bityutskiy
2009-05-11 7:23 ` Artem Bityutskiy
2009-05-11 7:37 ` Mike Frysinger
2009-05-11 7:58 ` Corentin Chary
2009-05-11 14:29 ` Artem Bityutskiy
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=1242026390.27996.132.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=corentincj@iksaif.net \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox