From: Masahiro Yamada <masahiroy@kernel.org>
To: David Gow <davidgow@google.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v1 1/1] .gitignore: Unignore .kunitconfig
Date: Sat, 28 Jan 2023 23:37:19 +0900 [thread overview]
Message-ID: <CAK7LNASsnDymUS=Pyo77g=0v58fMn38PY66A887nC8_E6_qXAg@mail.gmail.com> (raw)
In-Reply-To: <CABVgOSmZsAQcf6Ou_tyZL=hpiJcxMxXzmMfV5wRyCPBsb_d0UQ@mail.gmail.com>
On Sat, Jan 28, 2023 at 3:56 PM David Gow <davidgow@google.com> wrote:
>
> On Fri, 27 Jan 2023 at 22:56, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > There are almost dozen of .kunitconfig files that are ignored but
> > tracked. Unignore them.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
>
> Thanks! Only the original root-directory .kunitignore file was
> intended to be ignored, and that's no longer as important, and is now
> in the build dir anyway.
>
> Reviewed-by: David Gow <davidgow@google.com>
>
> Cheers,
> -- David
>
> > .gitignore | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/.gitignore b/.gitignore
> > index 22984d22d29e..e4f2ba0be516 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> > @@ -100,6 +100,7 @@ modules.order
> > !.get_maintainer.ignore
> > !.gitattributes
> > !.gitignore
> > +!.kunitconfig
> > !.mailmap
> > !.rustfmt.toml
> >
> > --
> > 2.39.0
> >
Why is this a dot file in the first place?
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2023-01-28 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 14:57 [PATCH v1 1/1] .gitignore: Unignore .kunitconfig Andy Shevchenko
2023-01-28 6:55 ` David Gow
2023-01-28 14:37 ` Masahiro Yamada [this message]
2023-01-31 0:00 ` David Gow
2023-01-31 2:11 ` Masahiro Yamada
2023-01-31 2:38 ` David Gow
2023-03-10 15:30 ` Andy Shevchenko
2023-03-31 8:18 ` David Gow
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='CAK7LNASsnDymUS=Pyo77g=0v58fMn38PY66A887nC8_E6_qXAg@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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).