From: Markus Elfring <Markus.Elfring@web.de>
To: Wang YanQing <udknight@gmail.com>, Joe Perches <joe@perches.com>,
Andy Whitcroft <apw@canonical.com>,
kernel-janitors@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Matteo Croce <mcroce@redhat.com>
Subject: Re: [PATCH v6] checkpatch: add support to check 'Fixes:' tag format
Date: Mon, 4 May 2020 11:45:02 +0200 [thread overview]
Message-ID: <38251b1f-e89b-7b3a-6045-f5ce1dc2596a@web.de> (raw)
In-Reply-To: <20200504082002.GA29972@udknight>
> v6:
…
> 2: Fix a typo issue, reported by …
> 3: Reword some diagnostics info.
Such small improvements are nice.
> 4: Add support to check and emit sensible diagnostics
> info for description which spans across more than
> two lines.
My software concerns are growing also for the preferred dependency management.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=0e698dfa282211e414076f9dc7e83c1c288314fd#n138
> 5: Avoid the word "acrosses", suggested by …
Another bit of collateral evolution.
But it seems that further suggestions and ideas need more efforts
to get the desired software development attention (I hope for a while).
Will the clarification and integration of possibly remaining open issues
continue in constructive ways?
Regards,
Markus
next prev parent reply other threads:[~2020-05-04 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 8:20 Wang YanQing
2020-05-04 9:45 ` Markus Elfring [this message]
2020-05-04 10:22 ` Wang YanQing
2020-05-04 11:17 ` [v6] " Markus Elfring
2020-05-04 18:34 ` [PATCH v6] " Joe Perches
2020-05-23 2:30 ` Wang YanQing
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=38251b1f-e89b-7b3a-6045-f5ce1dc2596a@web.de \
--to=markus.elfring@web.de \
--cc=alexei.starovoitov@gmail.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=udknight@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
all inboxes | Powered by JetHome®