From: "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
To: <ben.hutchings@codethink.co.uk>
Cc: <cip-dev@lists.cip-project.org>
Subject: Fw: [cip-dev] improve show-description results
Date: Fri, 25 Sep 2020 04:29:51 +0000 [thread overview]
Message-ID: <OSBPR01MB2053E88297084B0A7C265B58D0360@OSBPR01MB2053.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1637EAD4F9798B33.26834@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Sorry Ben, it seems that I misspelled your e-mail address.
I sent 3 patches for cip-kernel-sec to cip-dev.
Kind regards,
Daniel
________________________________________
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> on behalf of Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
Sent: Friday, September 25, 2020 12:59 PM
To: sz.lin@moxa.com; ben.hutchings@codethink.co.u; wens@csie.org
Cc: cip-dev@lists.cip-project.org
Subject: [cip-dev] improve show-description results
I had this in the backlog for a long time. These
patches, improve the way CVEs' descriptions are displayed
when calling scripts/report_affected.py with the option
--show-description` enabled.
[1/3] report_affected: word-wrap for the 'description'
[2/3] report_affected: Delete extra blank lines
[3/3] issues: fill in the description field of
Thanks,
Daniel
[-- Attachment #2: ATT00001.txt --]
[-- Type: text/plain, Size: 423 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5472): https://lists.cip-project.org/g/cip-dev/message/5472
Mute This Topic: https://lists.cip-project.org/mt/77073039/1050690
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129059/536130045/xyzzy [daniel.sangorrin@toshiba.co.jp]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #3: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5476): https://lists.cip-project.org/g/cip-dev/message/5476
Mute This Topic: https://lists.cip-project.org/mt/77073393/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
parent reply other threads:[~2020-09-25 4:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1637EAD4F9798B33.26834@lists.cip-project.org>]
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=OSBPR01MB2053E88297084B0A7C265B58D0360@OSBPR01MB2053.jpnprd01.prod.outlook.com \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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 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).