git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSoC][PATCH] git-ci: use pylint to analyze the git-p4 code

From
VTViet Hung Tran <viethtran1620@gmail.com>
Date
Mar 14, 2018, 00:44 UTC
Message-ID
<20180314004441.5075-1-viethtran1620@gmail.com>
In-Reply-To
<CAE5ih78HdDvN+x94H3Tzygis8QGROUe4B-yBubFH4simN2u9vQ@mail.gmail.com>
Hello Mr. Diamand,

I see. Initially, I also thought of using .pylintrc but I don’t know which error should be ignored and which should be fixed so I decided to adhere 100% to the convention and fix each type of errors in different patches.

Thank you for your help,
Viet
Signed-off-by: Viet Hung Tran <viethtran1620@gmail.com>
Previous: Luke DiamandNext: Viet Hung Tran
Message 6 of 8 in “git-ci: use pylint to analyze the git-p4 code”
  1. git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 12, 2018
  2. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 12, 2018
  3. Lars SchneiderMar 12, 2018
  4. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 13, 2018
  5. Luke DiamandMar 13, 2018
  6. [GSoC][PATCH] git-ci: use pylint to analyze the git-p4 codeViet Hung Tran, Mar 14, 2018
  7. [GSoC][PATCH 1/2] git-ci: add .pylintrc fileViet Hung Tran, Mar 14, 2018
  8. [GSoC][PATCH 2/2] git-ci: update .pylintrc to ignore current warningViet Hung Tran, Mar 14, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.