git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Cc: "Ramsay Jones" <ramsay@ramsayjones.plus.com>,
	"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci: run `make sparse` as a GitHub workflow
Date: Tue, 13 Jul 2021 13:34:26 -0400	[thread overview]
Message-ID: <f305f586-c3ac-a2ef-8769-5468a4c3e539@gmail.com> (raw)
In-Reply-To: <pull.994.git.1626177086682.gitgitgadget@gmail.com>

Hi Dscho,

Le 2021-07-13 à 07:51, Johannes Schindelin via GitGitGadget a écrit :
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
> 
> Occasionally we receive reviews after patches were integrated, where
> `sparse` identified problems such as file-local variables or functions
> being declared as global.
> 
> By running `sparse` 

maybe here, we could add a link to https://sparse.docs.kernel.org/en/latest/,
so interested readers who do not know about "sparse" can go and learn
about it ?

> as part of our Continuous Integration, we can catch
> such things much earlier. Even better: developers who activated GitHub
> Actions on their forks can catch such issues before even sending their
> patches to the Git mailing list.
> 
> This addresses https://github.com/gitgitgadget/git/issues/345
> 
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

> +    - name: Download the `sparse` package
> +      uses: git-for-windows/get-azure-pipelines-artifact@v0
> +      with:
> +        repository: git/git
> +        definitionId: 10
> +        artifact: sparse-20.04
> +    - name: Install the `sparse` package
> +      run: sudo dpkg -i sparse-20.04/sparse_*.deb

Out of curiosity, why is this necessary (as opposed to using
the Ubuntu package, i.e. 'sudo apt-get -q -y sparse') ?

Thanks,
Philippe.

  parent reply	other threads:[~2021-07-13 17:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 11:51 [PATCH] ci: run `make sparse` as a GitHub workflow Johannes Schindelin via GitGitGadget
2021-07-13 16:55 ` Đoàn Trần Công Danh
2021-07-14  9:12   ` Johannes Schindelin
2021-07-13 17:34 ` Philippe Blain [this message]
2021-07-14  9:09   ` Johannes Schindelin
2021-07-14 10:13     ` Johannes Schindelin
2021-07-16  1:37       ` Ramsay Jones
2021-07-13 22:41 ` Junio C Hamano
2021-07-14 10:09   ` Johannes Schindelin
2021-07-14 16:00     ` Junio C Hamano
2021-07-14 20:54       ` Johannes Schindelin
2021-07-14 20:56         ` Junio C Hamano
2021-07-14 22:03           ` Johannes Schindelin
2021-07-14 22:27             ` Junio C Hamano
2021-07-16 15:25               ` Johannes Schindelin
2021-07-16 16:42                 ` Junio C Hamano
2021-07-14 11:50 ` [PATCH v2] ci: run `make sparse` as part of the " Johannes Schindelin via GitGitGadget
2021-07-26 17:53   ` [PATCH] ci: run "apt-get update" before "apt-get install" Jeff King
2021-07-26 18:22     ` Jeff King
2021-07-26 22:12     ` Junio C Hamano
2021-07-26 20:27   ` [PATCH v3] ci: run `make sparse` as part of the GitHub workflow Johannes Schindelin via GitGitGadget
2021-07-26 22:20     ` Junio C Hamano

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=f305f586-c3ac-a2ef-8769-5468a4c3e539@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=ramsay@ramsayjones.plus.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).