From: Anthony PERARD <anthony.perard@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Bernhard Kaindl" <bernhard.kaindl@citrix.com>
Subject: Re: [PATCH 1/7] tools/python: Drop pylintrc
Date: Thu, 16 Mar 2023 11:23:01 +0000 [thread overview]
Message-ID: <45cc32f5-5b10-41e0-8489-df3cce8d9e78@perard> (raw)
In-Reply-To: <20230314141520.3652451-2-andrew.cooper3@citrix.com>
On Tue, Mar 14, 2023 at 02:15:14PM +0000, Andrew Cooper wrote:
> This was added in 2004 in c/s b7d4a69f0ccb5 and has never been referenced
> since. Given the the commit message of simply "Added .", it was quite
> possibly a mistake in the first place.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Well, "pylintrc" seems to be a config file to be used by `pylint`, but
there's also no reference to it. So removing the file seems a good
option.
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
--
Anthony PERARD
next prev parent reply other threads:[~2023-03-16 11:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 14:15 [PATCH 0/7] tools: More Python 3 fixes (part 1 of N) Andrew Cooper
2023-03-14 14:15 ` [PATCH 1/7] tools/python: Drop pylintrc Andrew Cooper
2023-03-16 11:23 ` Anthony PERARD [this message]
2023-03-16 18:00 ` Marek Marczykowski-Górecki
2023-03-14 14:15 ` [PATCH 2/7] tools/misc: Drop xencons Andrew Cooper
2023-03-16 11:33 ` Anthony PERARD
2023-03-16 12:05 ` Andrew Cooper
2023-03-16 18:01 ` Marek Marczykowski-Górecki
2023-03-14 14:15 ` [PATCH 3/7] tools: Delete trailing whitespace in python scripts Andrew Cooper
2023-03-16 11:35 ` Anthony PERARD
2023-03-16 18:02 ` Marek Marczykowski-Górecki
2023-03-14 14:15 ` [PATCH 4/7] tools/pygrub: Factor out common setup.py parts Andrew Cooper
2023-03-16 11:39 ` Anthony PERARD
2023-03-14 14:15 ` [PATCH 5/7] tools: Use -s for python shebangs Andrew Cooper
2023-03-14 14:50 ` Andrew Cooper
2023-03-16 12:15 ` Anthony PERARD
2023-03-16 19:37 ` [PATCH v2 " Andrew Cooper
2023-03-16 20:09 ` Marek Marczykowski-Górecki
2023-03-14 14:15 ` [PATCH 6/7] tools/python: Improve unit test handling Andrew Cooper
2023-03-16 18:06 ` Marek Marczykowski-Górecki
2023-03-14 14:15 ` [PATCH 7/7] tools/python: Drop shebangs from library files Andrew Cooper
2023-03-16 18:12 ` Marek Marczykowski-Górecki
2023-03-15 2:37 ` [PATCH 0/7] tools: More Python 3 fixes (part 1 of N) Henry Wang
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=45cc32f5-5b10-41e0-8489-df3cce8d9e78@perard \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=bernhard.kaindl@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.