From: Jacob Keller <jacob.keller@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Jacob Keller" <jacob.e.keller@intel.com>,
"Git mailing list" <git@vger.kernel.org>
Subject: Re: [PATCH v3] coccicheck: process every source file at once
Date: Fri, 5 Oct 2018 16:10:08 -0700 [thread overview]
Message-ID: <CA+P7+xpRt1j92m9y0pH-XLQ1_HaUZ97D7GEKJYJQCz83y=6x0Q@mail.gmail.com> (raw)
In-Reply-To: <20181005190045.GA17482@sigill.intra.peff.net>
On Fri, Oct 5, 2018 at 12:00 PM Jeff King <peff@peff.net> wrote:
> That's OK, too, assuming people would actually want to use it. I'm also
> OK shipping this (with the "make -j" fix you suggested) and seeing if
> anybody actually complains. I assume there are only a handful of people
> running coccicheck in the first place.
>
> -Peff
Ok. I can go this route if we have consensus on the "break it and see
if someone complains" route.
Regards,
Jake
next prev parent reply other threads:[~2018-10-05 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 20:07 [PATCH v3] coccicheck: process every source file at once Jacob Keller
2018-10-02 20:18 ` Jacob Keller
2018-10-05 2:17 ` Jacob Keller
2018-10-05 12:40 ` SZEDER Gábor
2018-10-05 16:25 ` Jeff King
2018-10-05 16:53 ` Keller, Jacob E
2018-10-05 16:59 ` Jeff King
2018-10-05 18:50 ` SZEDER Gábor
2018-10-05 19:00 ` Jeff King
2018-10-05 23:10 ` Jacob Keller [this message]
2018-10-06 8:42 ` René Scharfe
2018-10-09 3:11 ` Jeff King
2018-10-05 18:39 ` SZEDER Gábor
2018-10-05 19:02 ` Jeff King
2018-10-05 19:54 ` SZEDER Gábor
2018-10-09 3:15 ` Jeff King
2018-10-10 11:44 ` SZEDER Gábor
2018-10-10 13:59 ` Jeff King
2018-10-07 11:36 ` Beat Bolli
2018-10-07 11:49 ` Beat Bolli
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='CA+P7+xpRt1j92m9y0pH-XLQ1_HaUZ97D7GEKJYJQCz83y=6x0Q@mail.gmail.com' \
--to=jacob.keller@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=peff@peff.net \
--cc=szeder.dev@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.
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.