All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: git@vger.kernel.org
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: [PATCH 0/2] Remove unnecessary inclusions of parse-options.h from headers
Date: Sun, 19 Mar 2023 17:27:10 +0100	[thread overview]
Message-ID: <20230319162712.654137-1-szeder.dev@gmail.com> (raw)

Some source files use parse_options(), but don't include
parse-options.h, while some headers do include parse-options.h, though
don't really need it.  These patches fix these issues.

This series has a small and simple conflict with the 'ds/ahead-behind'
topic, and it will have small conflicts with Elijah's header cleanup
series as well:

  https://public-inbox.org/git/pull.1493.git.1679207282.gitgitgadget@gmail.com/T/#t


SZEDER Gábor (2):
  treewide: include parse-options.h in source files
  treewide: remove unnecessary inclusions of parse-options.h from
    headers

 builtin/ls-remote.c           | 1 +
 builtin/pack-objects.c        | 1 +
 builtin/receive-pack.c        | 1 +
 builtin/reflog.c              | 1 +
 builtin/send-pack.c           | 1 +
 diagnose.c                    | 1 +
 diagnose.h                    | 3 ++-
 list-objects-filter-options.c | 1 +
 list-objects-filter-options.h | 3 ++-
 ref-filter.h                  | 2 +-
 remote.c                      | 1 +
 remote.h                      | 2 +-
 revision.c                    | 1 +
 revision.h                    | 3 ++-
 send-pack.c                   | 1 +
 15 files changed, 18 insertions(+), 5 deletions(-)

-- 
2.40.0.499.g88fa0b00d2


             reply	other threads:[~2023-03-19 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 16:27 SZEDER Gábor [this message]
2023-03-19 16:27 ` [PATCH 1/2] treewide: include parse-options.h in source files SZEDER Gábor
2023-03-19 16:27 ` [PATCH 2/2] treewide: remove unnecessary inclusions of parse-options.h from headers SZEDER Gábor
2023-03-20 16:41 ` [PATCH 0/2] Remove " Elijah Newren

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=20230319162712.654137-1-szeder.dev@gmail.com \
    --to=szeder.dev@gmail.com \
    --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.
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.