Re: [PATCH] commit: make --only --allow-empty work without paths

From: Jeff King <peff@peff.net>
Date: Dec 3, 2016, 16:23 UTC
Message-ID: <20161203162318.uv27n4uhylobegto@sigill.intra.peff.net>
In-Reply-To: <20161203065949.GG19570@inner.h.apk.li>

On Sat, Dec 03, 2016 at 07:59:49AM +0100, Andreas Krey wrote:

Show 11 quoted lines

> > OK. I'm not sure why you would want to create an empty commit in such a
> > case.
> 
> User: Ok tool, make me a pullreq.
> 
> Tool: But you haven't mentioned any issue
>       in your commit messages. Which are they?
> 
> User: Ok, that would be A-123.
> 
> Tool: git commit --allow-empty -m 'FIX: A-123'

OK. I think "tool" is slightly funny here, but I get that is part of the real world works. Thanks for illustrating.

Show 7 quoted lines

> > Yes, I think --run is a misfeature (I actually had to look it up, as I
> ...
> > implicit. If a single test script is annoyingly long to run, I'd argue
> 
> It wasn't about runtime but about output. I would have
> liked to see only the output of my still-failing test;
> a 'stop after test X' would be helpful there.

You can do --verbose-only=<n>, but if the test is failing, I typically use "-v -i". That makes everything verbose, and then stops at the failing test, so you can see the output easily.

-Peff