cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Chen-Yu Tsai (Moxa)" <wens@csie.org>
To: cip-dev@lists.cip-project.org
Cc: "SZ Lin (林上智)" <sz.lin@moxa.com>,
	"Ben Hutchings" <ben.hutchings@codethink.co.uk>
Subject: Re: [cip-dev] [cip-kernel-sec 2/3] report_affected: Delete extra blank lines between CVEs
Date: Thu, 8 Oct 2020 15:59:58 +0800	[thread overview]
Message-ID: <CAGb2v67PutE3wGTOnQMy3FSzWD9uUGth1PF6=wJNY0nRfrn-bg@mail.gmail.com> (raw)
In-Reply-To: <20200925035927.1958987-3-daniel.sangorrin@toshiba.co.jp>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Fri, Sep 25, 2020 at 12:00 PM Daniel Sangorrin
<daniel.sangorrin@toshiba.co.jp> wrote:
>
> From: nguyen van hieu <hieu2.nguyenvan@toshiba.co.jp>
>
> When using the --show-description option CVEs had blank
> lines between them. Remove them to make it more compact.
>
> Signed-off-by: nguyen van hieu <hieu2.nguyenvan@toshiba.co.jp>
> Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>

Reviewed-by: Chen-Yu Tsai (Moxa) <wens@csie.org>

Though these occurrences seem to be very rare.

> ---
>  scripts/report_affected.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/report_affected.py b/scripts/report_affected.py
> index a181d97..9894602 100755
> --- a/scripts/report_affected.py
> +++ b/scripts/report_affected.py
> @@ -141,7 +141,7 @@ def main(git_repo, remotes, only_fixed_upstream,
>                  wrap_description = ''
>                  for line in textwrap.wrap(description, 80, break_long_words=False):
>                      wrap_description += line + '\n  '
> -                print(cve_id, '=>',wrap_description)
> +                print(cve_id, '=>',wrap_description.strip())
>          else:
>              print('%s:' % branch['full_name'], *sorted_cve_ids)
>
> --
> 2.25.1
>
>
> 
>

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5510): https://lists.cip-project.org/g/cip-dev/message/5510
Mute This Topic: https://lists.cip-project.org/mt/77073065/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]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2020-10-08  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  3:59 [cip-dev] improve show-description results Daniel Sangorrin
2020-09-25  3:59 ` [cip-dev] [cip-kernel-sec 1/3] report_affected: word-wrap for the 'description' Daniel Sangorrin
2020-10-08  7:58   ` Chen-Yu Tsai (Moxa)
2020-09-25  3:59 ` [cip-dev] [cip-kernel-sec 2/3] report_affected: Delete extra blank lines between CVEs Daniel Sangorrin
2020-10-08  7:59   ` Chen-Yu Tsai (Moxa) [this message]
2020-10-08  8:00     ` Chen-Yu Tsai (Moxa)
2020-09-25  3:59 ` [cip-dev] [cip-kernel-sec 3/3] issues: fill in the description field of remaining CVEs Daniel Sangorrin
2020-10-08  8:18   ` Chen-Yu Tsai (Moxa)
2020-10-14  4:16     ` Daniel Sangorrin
2020-10-14  4:21       ` Chen-Yu Tsai (Moxa)
2020-09-30  3:29 ` [cip-dev] improve show-description results Chen-Yu Tsai (Moxa)

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='CAGb2v67PutE3wGTOnQMy3FSzWD9uUGth1PF6=wJNY0nRfrn-bg@mail.gmail.com' \
    --to=wens@csie.org \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    --cc=sz.lin@moxa.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).