From: Laszlo Ersek <lersek@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, pkrempa@redhat.com,
qemu-block@nongnu.org, mst@redhat.com, mreitz@redhat.com,
pbonzini@redhat.com, marcandre.lureau@redhat.com,
philmd@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 06/12] vl: Factor configure_blockdev() out of main()
Date: Fri, 8 Mar 2019 09:31:13 +0100 [thread overview]
Message-ID: <d48e2cc0-6179-83d5-c498-5e3394a2246c@redhat.com> (raw)
In-Reply-To: <87o96mmrj4.fsf@dusky.pond.sub.org>
On 03/07/19 20:08, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
>
>> On 3/7/19 11:23 AM, Markus Armbruster wrote:
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>>
>>> # Conflicts:
>>> # vl.c
>>
>> How'd you get git to preserve the leading #? Generally, I find conflicts
>> details useful for cherry-picked backports, but pointless for rebased
>> patches intended as original upstream material. And git defaults to
>> stripping lines with leading # when composing a commit message.
>
> I've messed up too many commit message by having fill-paragraph flow a #
> to the beginning of a line, so I added
>
> [commit]
> cleanup = scissors
I'm going to steal this now. :)
>
> to my .gitconfig. I've been messing up commit messages with leftover
> crap ever since, but leftover crap has proven less confusing to my
> reviewers than missing lines.
>
>> May be
>> worth cleaning up before the actual pull request.
>
> Certainly.
>
>
> git-commit(1):
>
> --cleanup=<mode>
> This option determines how the supplied commit message should be
> cleaned up before committing. The <mode> can be strip, whitespace,
> verbatim, scissors or default.
>
> strip
> Strip leading and trailing empty lines, trailing whitespace,
> commentary and collapse consecutive empty lines.
>
> whitespace
> Same as strip except #commentary is not removed.
>
> verbatim
> Do not change the message at all.
>
> scissors
> Same as whitespace except that everything from (and including)
> the line found below is truncated, if the message is to be
> edited. "#" can be customized with core.commentChar.
>
> # ------------------------ >8 ------------------------
>
> default
> Same as strip if the message is to be edited. Otherwise
> whitespace.
>
> The default can be changed by the commit.cleanup configuration
> variable (see git-config(1)).
>
Yeah I can tell this documentation was written by a programmer. The
documentation most likely follows the implementation closely (nested
"if"s?), with the "double except". Just try to expand the definition of
"scissors" without a mental stack overflow:
Same as strip except #commentary is not removed except that
everything from (and including) the line found below is truncated
Geez.
Anyway, thank you again for the tip!
Laszlo
next prev parent reply other threads:[~2019-03-08 8:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 17:23 [Qemu-devel] [PATCH v2 00/12] pc: Support firmware configuration with -blockdev Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 01/12] qdev: Fix latent bug with compat_props and onboard devices Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 02/12] qom: Move compat_props machinery from qdev to QOM Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 03/12] vl: Fix latent bug with -global and onboard devices Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 04/12] sysbus: Fix latent bug with " Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 05/12] vl: Improve legibility of BlockdevOptions queue Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 06/12] vl: Factor configure_blockdev() out of main() Markus Armbruster
2019-03-07 17:46 ` Philippe Mathieu-Daudé
2019-03-07 17:59 ` Eric Blake
2019-03-07 19:08 ` Markus Armbruster
2019-03-08 8:31 ` Laszlo Ersek [this message]
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 07/12] vl: Create block backends before setting machine properties Markus Armbruster
2019-03-07 17:46 ` Philippe Mathieu-Daudé
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 08/12] pflash_cfi01: Add pflash_cfi01_get_blk() helper Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 09/12] pc_sysfw: Remove unused PcSysFwDevice Markus Armbruster
2019-03-07 17:23 ` [Qemu-devel] [PATCH v2 10/12] pc_sysfw: Pass PCMachineState to pc_system_firmware_init() Markus Armbruster
2019-03-08 8:11 ` Laszlo Ersek
2019-03-07 17:24 ` [Qemu-devel] [PATCH v2 11/12] pc: Support firmware configuration with -blockdev Markus Armbruster
2019-03-07 17:48 ` Philippe Mathieu-Daudé
2019-03-08 8:22 ` Laszlo Ersek
2019-03-07 17:24 ` [Qemu-devel] [PATCH v2 12/12] docs/interop/firmware.json: Prefer -machine to if=pflash Markus Armbruster
2019-03-08 8:44 ` Laszlo Ersek
2019-03-08 12:01 ` Markus Armbruster
2019-03-07 17:49 ` [Qemu-devel] [PATCH v2 00/12] pc: Support firmware configuration with -blockdev no-reply
2019-03-07 18:29 ` no-reply
2019-03-07 18:46 ` no-reply
2019-03-08 8:17 ` no-reply
2019-03-08 8:26 ` no-reply
2019-03-09 0:56 ` no-reply
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=d48e2cc0-6179-83d5-c498-5e3394a2246c@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 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 NNTP newsgroup(s).