git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Alejandro R. Sedeño" <asedeno@mit.edu>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	"Aleajndro R Sedeño" <asedeno@google.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] git-compat-util.h: GCC deprecated only takes a message in GCC 4.5+
Date: Thu, 6 Oct 2022 08:16:24 -0400	[thread overview]
Message-ID: <Yz7HGAThrOcPdmjm@coredump.intra.peff.net> (raw)
In-Reply-To: <221006.86lepts927.gmgdl@evledraar.gmail.com>

On Thu, Oct 06, 2022 at 09:29:11AM +0200, Ævar Arnfjörð Bjarmason wrote:

> > This will cause some mild hardships, as later patches will need to
> > #define UNUSED in other spots, as well, in order to get full coverage of
> > the code base (I have written those annotation patches, but they're not
> > applied upstream yet).
> 
> Sorry about any trouble in having to rebase those on UNUSED.

That part was not too bad, and is already done.

The trickiest part is that the headers get included in odd orders, and
if the macros don't match, the compiler will complain (this has to do
with compat/ headers which don't necessarily start by including
git-compat-util.h).

But if the definition gets much more complicated, then it's probably
worth pulling it out rather than repeating it.

> If you're taking requests it would be really useful to prioritize
> changes to shared headers and the like, e.g. DEVOPTS=extra-all on pretty
> much any file will start with:
> 	
> 	git-compat-util.h: In function ‘precompose_argv_prefix’:
> 	git-compat-util.h:313:54: error: unused parameter ‘argc’ [-Werror=unused-parameter]
> 	  313 | static inline const char *precompose_argv_prefix(int argc, const char **argv, const char *prefix)
> 	      |                                                  ~~~~^~~~
> 	git-compat-util.h:313:73: error: unused parameter ‘argv’ [-Werror=unused-parameter]
> 	  313 | static inline const char *precompose_argv_prefix(int argc, const char **argv, const char *prefix)
> 	      |                                                            ~~~~~~~~~~~~~^~~~
> 	git-compat-util.h: In function ‘git_has_dos_drive_prefix’:
> 	git-compat-util.h:423:56: error: unused parameter ‘path’ [-Werror=unused-parameter]
> 	  423 | static inline int git_has_dos_drive_prefix(const char *path)
> 	      |                                            ~~~~~~~~~~~~^~~~
> 	git-compat-util.h: In function ‘git_skip_dos_drive_prefix’:
> 	git-compat-util.h:431:52: error: unused parameter ‘path’ [-Werror=unused-parameter]
> 	  431 | static inline int git_skip_dos_drive_prefix(char **path)

Yeah, those are near the top of my list. I have a group classified as
"trivial": functions which are compat placeholders and have no body.
I'll be mostly offline for about a week, but I hope to send another
round of unused-mark patches when I get back. (Of course it is not
really useful until _all_ of the patches are there anyway).

-Peff

  reply	other threads:[~2022-10-06 12:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 21:23 [PATCH] git-compat-util.h: GCC deprecated only takes a message in GCC 4.5+ Aleajndro R Sedeño
2022-10-03 22:25 ` brian m. carlson
2022-10-03 23:45   ` Alejandro R. Sedeño
2022-10-05 14:53     ` Jeff King
2022-10-06  7:29       ` Ævar Arnfjörð Bjarmason
2022-10-06 12:16         ` Jeff King [this message]
2022-10-06 21:15           ` Ævar Arnfjörð Bjarmason
2022-10-11  0:22             ` Jeff King
     [not found]   ` <xmqqilkynd91.fsf@gitster.g>
2022-10-05 22:19     ` [PATCH] git-compat-util.h: GCC deprecated message arg only " Aleajndro R Sedeño
2022-10-06  7:31       ` Ævar Arnfjörð Bjarmason
2022-10-06 12:24         ` Alejandro R. Sedeño
2022-10-05 22:22     ` [PATCH] git-compat-util.h: GCC deprecated only takes a message " Alejandro R. Sedeño
2022-10-06  7:33   ` Ævar Arnfjörð Bjarmason

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yz7HGAThrOcPdmjm@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=asedeno@google.com \
    --cc=asedeno@mit.edu \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).