From: Garrit Franke <garrit@slashdev.space>
To: git@vger.kernel.org
Cc: Garrit Franke <garrit@slashdev.space>
Subject: [PATCH] bisect.c: remove unused includes
Date: Thu, 31 Mar 2022 21:44:36 +0200 [thread overview]
Message-ID: <20220331194436.58005-1-garrit@slashdev.space> (raw)
Clean up includes no longer needed by bisect.c.
Signed-off-by: Garrit Franke <garrit@slashdev.space>
---
bisect.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/bisect.c b/bisect.c
index 9e6a2b7f20..e07e2d215d 100644
--- a/bisect.c
+++ b/bisect.c
@@ -1,21 +1,12 @@
-#include "cache.h"
#include "config.h"
-#include "commit.h"
-#include "diff.h"
-#include "revision.h"
#include "refs.h"
#include "list-objects.h"
#include "quote.h"
-#include "hash-lookup.h"
#include "run-command.h"
#include "log-tree.h"
#include "bisect.h"
-#include "oid-array.h"
-#include "strvec.h"
-#include "commit-slab.h"
#include "commit-reach.h"
#include "object-store.h"
-#include "dir.h"
static struct oid_array good_revs;
static struct oid_array skipped_revs;
--
2.35.1
next reply other threads:[~2022-03-31 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:44 Garrit Franke [this message]
2022-03-31 21:29 ` [PATCH] bisect.c: remove unused includes Junio C Hamano
2022-04-01 8:07 ` using iwyu (include-what-you-use) to analyze includes (was: [PATCH] bisect.c: remove unused includes) Ævar Arnfjörð Bjarmason
2022-04-05 11:45 ` [PATCH v2 0/4] various: use iwyu (include-what-you-use) to analyze includes Garrit Franke
2022-04-06 7:54 ` Ævar Arnfjörð Bjarmason
2022-04-05 11:45 ` [PATCH v2 1/4] contrib: add iwyu script Garrit Franke
2022-04-06 7:40 ` Ævar Arnfjörð Bjarmason
2022-04-05 11:45 ` [PATCH v2 2/4] bisect.c: remove unnecessary include Garrit Franke
2022-04-06 7:50 ` Ævar Arnfjörð Bjarmason
2022-04-06 16:41 ` Junio C Hamano
2022-04-05 11:45 ` [PATCH v2 3/4] serve.c: " Garrit Franke
2022-04-05 11:45 ` [PATCH v2 4/4] apply.c: " Garrit Franke
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=20220331194436.58005-1-garrit@slashdev.space \
--to=garrit@slashdev.space \
--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 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).