From: Markus Elfring <Markus.Elfring@web.de>
To: 唐彬 <tangbin@cmss.chinamobile.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: Clarification for software development opportunities
Date: Sun, 5 Apr 2020 07:44:01 +0200 [thread overview]
Message-ID: <95c5e77d-e993-f12e-11d6-9a43b9afc230@web.de> (raw)
In-Reply-To: <2020040505380926003012@cmss.chinamobile.com>
> I don't know what is Coccinelle software, I will check it out.
I am curious under which circumstances the development tool box will be adjusted.
http://coccinelle.lip6.fr/
> When I receive critical emails from others, I am happy that this is my study plan.
This view sounds positive.
> Previously, I was happy and looking forward to providing patches to the community.
Such feedback is nice.
> But when I noticed that you were sending similar patches over and over again,
This can be an usual effect from the application of known source code
analysis approaches.
> I realized that if I want to increase my patch count,
I suggest to reconsider corresponding development goals.
> I would not be able to reuse some files I had already found,
This can occasionally happen when some contributors try to achieve something
in similar areas.
* Would you like to clarify opportunities for further contributions?
* Do you find globally distributed collaboration interesting?
> which made me sad.
* I find your feeling unfortunate.
* I hope that your view can become more positive again.
> So,thank you for giving me a lesson.
This was eventually my intention partly.
I imagine that possibilities can be improved also for teaching and education.
Regards,
Markus
next prev parent reply other threads:[~2020-04-05 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 14:56 [PATCH] hwrng: omap - Delete an error message in of_get_omap_rng_device_details() Markus Elfring
[not found] ` <2020040423261552036811@cmss.chinamobile.com>
2020-04-04 16:49 ` Markus Elfring
[not found] ` <2020040505380926003012@cmss.chinamobile.com>
2020-04-05 5:44 ` Markus Elfring [this message]
2020-04-06 6:54 ` Markus Elfring
2020-04-16 6:51 ` [PATCH] " Herbert Xu
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=95c5e77d-e993-f12e-11d6-9a43b9afc230@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tangbin@cmss.chinamobile.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
all inboxes | Powered by JetHome®