From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: patman regression?
Date: Fri, 11 Dec 2020 12:37:22 +0800 [thread overview]
Message-ID: <CAEUhbmXHcg1EuYoDm9vCN7W_xvLyi-nVwAjrooaOe0dBySR-NA@mail.gmail.com> (raw)
In-Reply-To: <dd765aec-ca66-afa8-f602-87c9622ddbae@gmail.com>
On Fri, Dec 11, 2020 at 12:32 PM Sean Anderson <seanga2@gmail.com> wrote:
>
> On 12/10/20 11:27 PM, Bin Meng wrote:
> > On Fri, Dec 11, 2020 at 12:08 PM Bin Meng <bmeng.cn@gmail.com> wrote:
> >>
> >> Hi Simon,
> >>
> >> The following command no longer works. They used to work.
> >>
> >> $ ./tools/patman/patman -n -c1
> >> usage: patman [-h] [-b BRANCH] [-c COUNT] [-e END] [-D] [-p PROJECT]
> >> [-P PATCHWORK_URL] [-s START] [-v] [-H]
> >> {send,test,status} ...
> >> patman: error: unrecognized arguments: -n
> >> $ ./tools/patman/patman -n -c 1
> >> usage: patman [-h] [-b BRANCH] [-c COUNT] [-e END] [-D] [-p PROJECT]
> >> [-P PATCHWORK_URL] [-s START] [-v] [-H]
> >> {send,test,status} ...
> >> patman: error: argument -c/--count: invalid int value: 'send'
> >>
> >> I did not run a bisect to locate which commit introduced this. Do you
> >> have any idea?
> >
> > Resetting to v2020.10, patman works again with the above 2 commands.
> >
> > Note the latest patman also throws an exception about commit tags
> > while the v2020.10 version did not.
> >
> > Traceback (most recent call last):
> > File "./tools/patman/patman", line 177, in <module>
> > control.send(args)
> > File "./tools/patman/control.py", line 177, in send
> > args.smtp_server)
> > File "./tools/patman/control.py", line 136, in email_patches
> > add_maintainers, limit)
> > File "./tools//patman/series.py", line 264, in MakeCcFile
> > raise_on_error=raise_on_error)
> > File "./tools//patman/gitutil.py", line 383, in BuildEmailList
> > raw += LookupEmail(item, alias, raise_on_error=raise_on_error)
> > File "./tools//patman/gitutil.py", line 588, in LookupEmail
> > raise ValueError(msg)
> > ValueError: Alias 'doc' not found
>
> I also get this error even with process_tags=False.
Yep, here is my patman settings:
[settings]
ignore_errors: True
process_tags: False
verbose: True
Regards,
Bin
next prev parent reply other threads:[~2020-12-11 4:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 4:08 patman regression? Bin Meng
2020-12-11 4:27 ` Bin Meng
2020-12-11 4:32 ` Sean Anderson
2020-12-11 4:37 ` Bin Meng [this message]
2020-12-11 16:29 ` Simon Glass
2020-12-22 23:51 ` Sean Anderson
2020-12-23 0:06 ` Simon Glass
2020-12-23 0:38 ` Sean Anderson
2020-12-23 1:25 ` Bin Meng
2020-12-23 3:03 ` 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=CAEUhbmXHcg1EuYoDm9vCN7W_xvLyi-nVwAjrooaOe0dBySR-NA@mail.gmail.com \
--to=bmeng.cn@gmail.com \
--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.