All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] patman: make run results better visible
Date: Wed, 3 Sep 2014 21:25:59 -0700	[thread overview]
Message-ID: <CAD=FV=XYcEP0e2V2VG1A8wBS+3pbZD+VsQCQyz8kS4x2Byg=ug@mail.gmail.com> (raw)
In-Reply-To: <CAC3GErH689R9=_MTTDqNeJhG_vdncJTqMA-E_0PZaxRiB23Bng@mail.gmail.com>

Vadim,

On Wed, Sep 3, 2014 at 4:00 PM, Vadim Bendebury <vbendeb@chromium.org> wrote:
> On Wed, Sep 3, 2014 at 3:14 PM, Doug Anderson <dianders@chromium.org> wrote:
>> Vadim,
>>
>> On Wed, Sep 3, 2014 at 12:16 PM, Vadim Bendebury <vbendeb@chromium.org> wrote:
>>> For an occasional user of patman some failures are not obvious: for
>>> instance when checkpatch reports warnings, the dry run still reports
>>> that the email would be sent. If it is not dry run, the warnings are
>>> shown on the screen, but it is not clear that the email was not sent.
>>>
>>> Add some code to report failure to send email explicitly.
>>>
>>> Tested by running the script on a patch with style violations,
>>> observed error messages in the script output.
>>>
>>> Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
>>> ---
>>>
>>>  tools/patman/patman.py | 8 +++++++-
>>>  1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tools/patman/patman.py b/tools/patman/patman.py
>>> index c60aa5a..0163ccd 100755
>>> --- a/tools/patman/patman.py
>>> +++ b/tools/patman/patman.py
>>> @@ -154,13 +154,19 @@ else:
>>>
>>>      # Email the patches out (giving the user time to check / cancel)
>>>      cmd = ''
>>> -    if ok or options.ignore_errors:
>>> +    its_a_go = ok or options.ignore_errors
>>> +    if its_a_go:
>>>          cmd = gitutil.EmailPatches(series, cover_fname, args,
>>>                  options.dry_run, not options.ignore_bad_tags, cc_file,
>>>                  in_reply_to=options.in_reply_to)
>>> +    else:
>>> +        print col.Color(col.RED,
>>> +                        "Not sending emails due to checkpatch errors/warnings")
>>
>> Technically it could be due to other problems, too (like errors applying).
>
> good point, what wording would you suggest?

You don't think that just removing the word "checkpatch" is enough.

  reply	other threads:[~2014-09-04  4:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 19:16 [U-Boot] [PATCH] patman: make run results better visible Vadim Bendebury
2014-09-03 22:14 ` Doug Anderson
2014-09-03 23:00   ` Vadim Bendebury
2014-09-04  4:25     ` Doug Anderson [this message]
2014-09-04 17:45 ` [U-Boot] [PATCH v2] " Vadim Bendebury
2014-09-04 18:57   ` Doug Anderson
2014-09-04 22:38     ` Simon Glass
2014-09-10 18:55       ` Simon Glass

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='CAD=FV=XYcEP0e2V2VG1A8wBS+3pbZD+VsQCQyz8kS4x2Byg=ug@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.