From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Paul Szczepanek <paul.szczepanek@arm.com>,
Patrick Robb <probb@iol.unh.edu>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [RFC] git: consolidate .gitignore files
Date: Tue, 11 Feb 2025 09:38:49 +0100 [thread overview]
Message-ID: <1760201.izSxrag8PF@thomas> (raw)
In-Reply-To: <20250210172050.8884-1-stephen@networkplumber.org>
10/02/2025 18:20, Stephen Hemminger:
> +# ignore Linux UAPI kernel headers
> +kernel/linux/uapi/version
> +kernel/linux/uapi/**/*.h
The original .gitignore had some "!" for an opposite logic.
I think we can just completely drop this one, it looks unneeded.
next prev parent reply other threads:[~2025-02-11 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 18:26 [PATCH] devtools: ignore .gitignore in SPDX check Stephen Hemminger
2025-02-10 16:51 ` Thomas Monjalon
2025-02-10 17:20 ` [RFC] git: consolidate .gitignore files Stephen Hemminger
2025-02-11 8:38 ` Thomas Monjalon [this message]
2025-02-11 15:43 ` Patrick Robb
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=1760201.izSxrag8PF@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.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).