git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/4] a few small unused-parameter fixes
Date: Thu, 6 Oct 2022 09:09:35 -0400	[thread overview]
Message-ID: <Yz7Tjy7Rh8cXVxYQ@coredump.intra.peff.net> (raw)

These ones are not annotations of unused parameters, but rather code
changes that (I hope) make the world a better place while also silencing
-Wunused-parameters.

I've been trying to bubble these up to the front of my series of UNUSED
annotations. I _thought_ I had got all of them, but I think a few of
these are new, and some are ones that just got lost in the shuffle of
earlier series.

  [1/4]: test-submodule: inline resolve_relative_url() function
  [2/4]: multi-pack-index: avoid writing to global in option callback
  [3/4]: commit: avoid writing to global in option callback
  [4/4]: attr: convert DEBUG_ATTR to use trace API

 attr.c                     | 38 +++++++++++++++++---------------------
 builtin/commit.c           |  4 ++--
 builtin/multi-pack-index.c |  7 ++++---
 t/helper/test-submodule.c  | 22 ++++++++--------------
 4 files changed, 31 insertions(+), 40 deletions(-)

-Peff

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 13:09 Jeff King [this message]
2022-10-06 13:10 ` [PATCH 1/4] test-submodule: inline resolve_relative_url() function Jeff King
2022-10-06 13:10 ` [PATCH 2/4] multi-pack-index: avoid writing to global in option callback Jeff King
2022-10-06 13:11 ` [PATCH 3/4] commit: " Jeff King
2022-10-06 13:13 ` [PATCH 4/4] attr: convert DEBUG_ATTR to use trace API Jeff King
2022-10-06 13:23   ` [PATCH 4alt/4] attr: drop DEBUG_ATTR code Jeff King
2022-10-06 17:02     ` Junio C Hamano
2022-10-06 18:33       ` Derrick Stolee
2022-10-06 18:52         ` Junio C Hamano
2022-10-11  0:26         ` Jeff King
2022-10-11  0:23       ` Jeff King

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=Yz7Tjy7Rh8cXVxYQ@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.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.
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).