From: John Snow <jsnow@redhat.com>
To: Fam Zheng <fam@euphon.net>
Cc: philmd@redhat.com, alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docker: add sanitizers back to clang build
Date: Thu, 19 Sep 2019 15:16:43 -0400 [thread overview]
Message-ID: <371d715a-dfba-2535-cb16-c3bc08f90d97@redhat.com> (raw)
In-Reply-To: <20190918023826.GA28483@magic>
On 9/17/19 10:38 PM, Fam Zheng wrote:
> On Thu, 09/12 19:07, John Snow wrote:
>>
>>
>> On 9/11/19 9:52 PM, no-reply@patchew.org wrote:
>>> Patchew URL: https://patchew.org/QEMU/20190912014442.5757-1-jsnow@redhat.com/
>>>
>>>
>>>
>>> Hi,
>>>
>>> This series seems to have some coding style problems. See output below for
>>> more information:
>>>
>>> Subject: [Qemu-devel] [PATCH] docker: add sanitizers back to clang build
>>> Message-id: 20190912014442.5757-1-jsnow@redhat.com
>>> Type: series
>>>
>>> === TEST SCRIPT BEGIN ===
>>> #!/bin/bash
>>> git rev-parse base > /dev/null || exit 0
>>> git config --local diff.renamelimit 0
>>> git config --local diff.renames True
>>> git config --local diff.algorithm histogram
>>> ./scripts/checkpatch.pl --mailback base..
>>> === TEST SCRIPT END ===
>>>
>>> From https://github.com/patchew-project/qemu
>>> * [new tag] patchew/20190912014442.5757-1-jsnow@redhat.com -> patchew/20190912014442.5757-1-jsnow@redhat.com
>>> Switched to a new branch 'test'
>>> 96d44b9 docker: add sanitizers back to clang build
>>>
>>> === OUTPUT BEGIN ===
>>> ERROR: Missing Signed-off-by: line(s)
>>
>> GDI.
>>
>> I keep adding this to my configuration files, but it keeps "falling
>> off", somehow.
>>
>> I have some patches in the works for stgit where I'm going to work
>> through some test cases for setting profile variables and try to fix this.
>>
>> In the meantime:
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>
> Isn't this because you inserted a '---' line in the middle of the commit
> message so the part after it is ditched by 'git am'?
>
> This feels a bit hard to catch, wondering what is in the works. :)
>
gah, you're right -- I blamed it on the script failing, because it has
been a little unreliable for me lately :)
Hm, how do I accommodate putting in notes to my commit messages while
keeping tooling happy ...
--js
prev parent reply other threads:[~2019-09-19 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 1:44 [Qemu-devel] [PATCH] docker: add sanitizers back to clang build John Snow
2019-09-12 1:52 ` no-reply
2019-09-12 23:07 ` John Snow
2019-09-18 2:38 ` Fam Zheng
2019-09-19 19:16 ` John Snow [this message]
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=371d715a-dfba-2535-cb16-c3bc08f90d97@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--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).