Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Maíra Canal" <mcanal@igalia.com>,
	linux-kselftest@vger.kernel.org,
	"David Gow" <davidgow@google.com>,
	"Maxime Ripard" <maxime@cerno.tech>,
	"Enric Balletbo i Serra" <eballetbo@redhat.com>,
	kunit-dev@googlegroups.com,
	"Daniel Latypov" <dlatypov@google.com>,
	"Brendan Higgins" <brendanhiggins@google.com>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Andrew Davis" <afd@ti.com>, "Kees Cook" <keescook@chromium.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Wedson Almeida Filho" <wedsonaf@google.com>
Subject: [PATCH] .gitignore: Exclude KUnit config dot-files
Date: Thu, 30 Mar 2023 13:27:42 +0200	[thread overview]
Message-ID: <20230330112743.2331141-1-javierm@redhat.com> (raw)

There's a rule to ignore all the dot-files (.*) but we want to exclude the
config files used by KUnit (.kunitconfig) since those are usually added to
allow executing test suites without having to enable custom config symbols.

Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
---

 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 70ec6037fa7a..7f86e0837909 100644
--- a/.gitignore
+++ b/.gitignore
@@ -103,6 +103,7 @@ modules.order
 !.get_maintainer.ignore
 !.gitattributes
 !.gitignore
+!.kunitconfig
 !.mailmap
 !.rustfmt.toml
 

base-commit: ffe78bbd512166e0ef1cc4858010b128c510ed7d
-- 
2.40.0


             reply	other threads:[~2023-03-30 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 11:27 Javier Martinez Canillas [this message]
2023-03-30 11:33 ` [PATCH] .gitignore: Exclude KUnit config dot-files Maíra Canal
2023-03-30 15:34 ` Daniel Latypov
2023-03-30 16:55   ` Javier Martinez Canillas

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=20230330112743.2331141-1-javierm@redhat.com \
    --to=javierm@redhat.com \
    --cc=afd@ti.com \
    --cc=alex.gaynor@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=dlatypov@google.com \
    --cc=eballetbo@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mcanal@igalia.com \
    --cc=ojeda@kernel.org \
    --cc=wedsonaf@google.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox