From: Junio C Hamano <gitster@pobox.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] Remove. duplicate include directives
Date: Sun, 13 Mar 2022 22:22:16 +0000 [thread overview]
Message-ID: <xmqqzglttrvr.fsf@gitster.g> (raw)
In-Reply-To: <20220313195536.224075-1-gitter.spiros@gmail.com> (Elia Pinto's message of "Sun, 13 Mar 2022 19:55:31 +0000")
Elia Pinto <gitter.spiros@gmail.com> writes:
> This series of patches does not solve any particular problems but
> only eliminates unnecessary duplicate include directives
> from git sources
>
> Elia Pinto (5):
> attr.c: delete duplicate include
> builtin/gc.c: delete duplicate include
> builtin/sparse-checkout.c: delete duplicate include
> builtin/stash.c: delete duplicate include
> t/helper/test-run-command.c: delete duplicate include
Thanks.
It matches the output from the pipeline:
$ git grep '^#include' \*.c |
sort | uniq -c | sort -n | sed -e '/^ *1 /d'
prev parent reply other threads:[~2022-03-13 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 19:55 [PATCH 0/5] Remove. duplicate include directives Elia Pinto
2022-03-13 19:55 ` [PATCH 1/5] attr.c: delete duplicate include Elia Pinto
2022-03-13 19:55 ` [PATCH 2/5] builtin/gc.c: " Elia Pinto
2022-03-13 19:55 ` [PATCH 3/5] builtin/sparse-checkout.c: " Elia Pinto
2022-03-13 19:55 ` [PATCH 4/5] builtin/stash.c: " Elia Pinto
2022-03-13 19:55 ` [PATCH 5/5] t/helper/test-run-command.c: " Elia Pinto
2022-03-13 22:22 ` Junio C Hamano [this message]
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=xmqqzglttrvr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.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.
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).