Re: [PATCH] coccicheck: introduce 'pending' semantic patches
- From
SZEDER Gábor <szeder.dev@gmail.com>
- Date
- Nov 13, 2018, 16:02 UTC
- Message-ID
- <20181113160252.GF30222@szeder.dev>
- In-Reply-To
- <20181110001052.101290-1-sbeller@google.com>
On Fri, Nov 09, 2018 at 04:10:52PM -0800, Stefan Beller wrote:
Show 14 quoted lines
> From: SZEDER Gábor <szeder.dev@gmail.com> > > Teach `make coccicheck` to avoid patches named "*.pending.cocci" and > handle them separately in a new `make coccicheck-pending` instead. > This means that we can separate "critical" patches from "FYI" patches. > The former target can continue causing Travis to fail its static > analysis job, while the latter can let us keep an eye on ongoing > (pending) transitions without them causing too much fallout. > > Document the intended use-cases around these two targets. > As the process around the pending patches is not yet fully explored, > leave that out. > > Based-on-work-by: SZEDER Gábor <szeder.dev@gmail.com>
Hm, do I need to sign off? Well, I sign off now anyway, and then Junio can take it if necessary or just ignore it if not.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Show 6 quoted lines
> Signed-off-by: Stefan Beller <sbeller@google.com> > Signed-off-by: Junio C Hamano <gitster@pobox.com> > --- > > I dialed back on the workflow, as we may want to explore it first > before writing it down.
Yeah, I too think that's better to wait with the workflow details until we gather some experience about how it works out in practice.
Thanks for following it through.