From: Willy Tarreau <w@1wt.eu>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH RFC] tools/nolibc: Add gitignore to avoid git complaints about sysroot
Date: Tue, 24 Jan 2023 04:11:47 +0100 [thread overview]
Message-ID: <20230124031147.GA17865@1wt.eu> (raw)
In-Reply-To: <Y88xjSd2ZIpVIeHd@biznet-home.integral.gnuweeb.org>
On Tue, Jan 24, 2023 at 08:17:01AM +0700, Ammar Faizi wrote:
> On Mon, Jan 23, 2023 at 05:12:57PM -0800, Paul E. McKenney wrote:
> > On Tue, Jan 24, 2023 at 08:06:00AM +0700, Ammar Faizi wrote:
> > > On Mon, Jan 23, 2023 at 04:47:07PM -0800, Paul E. McKenney wrote:
> > > > Testing of nolibc can produce a tools/include/nolibc/sysroot file, which
> > > > is not known to git. Because it is automatically generated, there is no
> > > > reason for it to be known to git. Therefore, add a .gitignore to remove
> > > > it from git's field of view.
> > >
> > > Yeah, I hit the same "git status" complaint and have a pending patch
> > > for that too:
> > >
> > > https://github.com/ammarfaizi2/linux-block/commit/89bfe86a03c173863de12.patch
> > >
> > > ^ I'll drop this one.
> >
> > Actually, why don't we take yours? Either way, I have to change something
> > per your feedback below.
> >
> > No hurry, send it along when you normally would have.
>
> OK, I'll keep it then. Will send it together with my other patches later :-)
Sorry, I didn't notice it previously. Ack from me for either of your
patches of course. Ammar, please note that Paul's subject is a bit more
descriptive, so please consider updating when you resend.
Thanks!
Willy
prev parent reply other threads:[~2023-01-24 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 0:47 [PATCH RFC] tools/nolibc: Add gitignore to avoid git complaints about sysroot Paul E. McKenney
2023-01-24 1:06 ` Ammar Faizi
2023-01-24 1:12 ` Paul E. McKenney
2023-01-24 1:17 ` Ammar Faizi
2023-01-24 3:11 ` Willy Tarreau [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230124031147.GA17865@1wt.eu \
--to=w@1wt.eu \
--cc=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.