From: Artem Bityutskiy <dedekind1@gmail.com>
To: "stanley.miao" <stanley.miao@windriver.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Fix mtd-utils bugs
Date: Fri, 18 Jun 2010 13:24:23 +0300 [thread overview]
Message-ID: <1276856663.19028.447.camel@localhost> (raw)
In-Reply-To: <4C1B2B65.3090606@windriver.com>
On Fri, 2010-06-18 at 16:16 +0800, stanley.miao wrote:
> Artem Bityutskiy wrote:
> > On Sun, 2010-06-13 at 12:51 +0300, Artem Bityutskiy wrote:
> >
> >> On Fri, 2010-06-11 at 17:36 +0800, Stanley.Miao wrote:
> >>
> >>> <snip>
> >>>
> >> Please, make sure your submissions have proper version. I have limited
> >> amount of time and do not want to spend it figuring out which patch is
> >> the latest. Use the best kernel practices and apply prefix your stuff
> >> with [PATCHv3] or something like that.
> >>
> >> Could you please re-submit your latest version?
> >>
> >
> > Also, it is nice to put a short changelog, but I can live without it.
> >
>
> Is the subject of every emails is the short changelog you wanted ?
Hi,
Sorry, I do not understand the question. I do not need changelogs. I
just noted that there are best practices, and people use changelogs. You
can take a look at lkml archives at patch series from good kernel
hackers for example.
If you asked whether the changelog should be in each patch - no, just in
the "0" patch, and just short.
Anyway, I just want you to re-send your up-to-date patches as a separate
series with a v2 prefix.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-06-18 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 9:36 Fix mtd-utils bugs Stanley.Miao
2010-06-11 9:36 ` [PATCH 1/3] clean up the legacy interfaces in nandwrite.c Stanley.Miao
2010-06-11 9:36 ` [PATCH 2/3] Discard the legacy interface MEMGETOOBSEL in flash_eraseall Stanley.Miao
2010-06-11 9:36 ` [PATCH 3/3] Place the cleanmarker in OOB area according to the mode MTD_OOB_AUTO Stanley.Miao
2010-06-11 9:44 ` [PATCH 2/3] Discard the legacy interface MEMGETOOBSEL in flash_eraseall Joakim Tjernlund
[not found] ` <OFDBEF7A42.BA0205E8-ONC125773F.0034F62C-C125773F.00358229@LocalDomain>
2010-06-11 9:53 ` Joakim Tjernlund
2010-06-11 10:36 ` stanley.miao
2010-06-11 10:44 ` Joakim Tjernlund
2010-06-11 12:11 ` Joakim Tjernlund
2010-06-13 9:51 ` Fix mtd-utils bugs Artem Bityutskiy
2010-06-13 10:14 ` Artem Bityutskiy
2010-06-17 4:10 ` stanley.miao
2010-06-18 8:16 ` stanley.miao
2010-06-18 10:24 ` Artem Bityutskiy [this message]
2010-06-20 12:21 ` stanley.miao
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 4:45 Stanley.Miao
2010-02-04 7:25 ` stanley.miao
2010-02-15 13:36 ` 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=1276856663.19028.447.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stanley.miao@windriver.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;
as well as URLs for NNTP newsgroup(s).