From: Jeff King <peff@peff.net>
To: Andreas Krey <a.krey@gmx.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] commit: make --only --allow-empty work without paths
Date: Sat, 3 Dec 2016 11:23:18 -0500 [thread overview]
Message-ID: <20161203162318.uv27n4uhylobegto@sigill.intra.peff.net> (raw)
In-Reply-To: <20161203065949.GG19570@inner.h.apk.li>
On Sat, Dec 03, 2016 at 07:59:49AM +0100, Andreas Krey wrote:
> > 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.
> > 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
next prev parent reply other threads:[~2016-12-03 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:15 [PATCH] commit: make --only --allow-empty work without paths Andreas Krey
2016-12-03 4:32 ` Jeff King
2016-12-03 6:59 ` Andreas Krey
2016-12-03 16:23 ` Jeff King [this message]
2016-12-05 20:36 ` Junio C Hamano
2016-12-06 9:39 ` Andreas Krey
2016-12-05 20:52 ` Junio C Hamano
2016-12-08 13:50 ` [PATCH v2] " Andreas Krey
2016-12-08 16:47 ` Junio C Hamano
2016-12-09 4:10 ` [PATCH] commit: remove 'Clever' message for --only --amend Andreas Krey
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161203162318.uv27n4uhylobegto@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=a.krey@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).