From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: florian@mickler.org, greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: MAINTAINERS: a question about it
Date: Sat, 12 Feb 2011 21:29:26 +0800 [thread overview]
Message-ID: <20110212132924.GA3044@gmail.com> (raw)
In-Reply-To: <AANLkTikbS9dWOpw-sUKFV01mnMBrQof0rQO6sde+53qe@mail.gmail.com>
On Sat, Feb 12, 2011 at 09:23:23PM +0800, harryxiyou wrote:
> ---------- Forwarded message ----------
> From: Florian Mickler <florian@mickler.org>
> Date: 2011/2/12
> Subject: Re: MAINTAINERS: a question about it
> To: harryxiyou <harryxiyou@gmail.com>
> Cc: Tranlations maintainer for linux kernel <greg@kroah.com>
>
>
> On Sat, 12 Feb 2011 10:56:48 +0800
> harryxiyou <harryxiyou@gmail.com> wrote:
>
> > Hi greg, Florian,
> > I will try to do it. Thanks to your help. Maybe i will do it
> in
> > get_maintainers.pl or a private shell script.
> > I just want to check if anyone has done it :)
> >
> > Thanks.
> > Best regards.
> > Harry Wei.
> >
>
Hi florian,
Thanks to your reply ;)
> Ok. If the script can automatically sort the file, that would be cool.
It can only check if the maintainers in the alphabetical order when maintainer add himself in it.
>
> And a little note, because I don't know if you already know it:
> We almost never drop people from the 'cc:' list. That could be
> considered rude if that person is actually interested in the email
> thread. That is why we, if in doubt, keep the cc list.
Thanks, i will remember this rule. Keep the cc list :)
>
> Another thing that you can try, is to find a bug report with a
> backtrace, locate the bug in the source code and then try to figure out
> why it happened and how it could be prevented from happening. And then
> you can check if the solution somebody else probably already posted in
> the meantime is what you would have done. (Oh, and be warned, some
> people know what they do, and some don't... not easy to tell.. and it
> varies from day to day ;) )
I will surely do it later :) thanks to your help.
Thanks.
Best Regards.
Harry Wei.
>
> Regards,
> Flo
>
>
>
>
> --
> Best Regards.
> Harry Wei.
> Do what u like!
prev parent reply other threads:[~2011-02-12 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 12:29 MAINTAINERS: a question about it Harry Wei
2011-02-11 15:40 ` Greg KH
2011-02-11 21:14 ` Florian Mickler
2011-02-11 21:25 ` Greg KH
2011-02-11 23:43 ` Florian Mickler
[not found] ` <AANLkTikXxf8BDmf5gfOQ6T0OvR=_RUFdOiYEPZVJ2Pm2@mail.gmail.com>
[not found] ` <20110212140158.00c7faa3@schatten.dmk.lab>
[not found] ` <AANLkTikbS9dWOpw-sUKFV01mnMBrQof0rQO6sde+53qe@mail.gmail.com>
2011-02-12 13:29 ` Harry Wei [this message]
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=20110212132924.GA3044@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=florian@mickler.org \
--cc=greg@kroah.com \
--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 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.