From: Hannes Schmelzer <hannes@schmelzer.or.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] trouble with patman
Date: Mon, 15 Feb 2016 07:39:41 +0100 [thread overview]
Message-ID: <56C172AD.90405@schmelzer.or.at> (raw)
In-Reply-To: <CAPnjgZ3S7bknV=BnUA2jW+-EFC2XDc6u1Xnv_MCftWP=RWrW9g@mail.gmail.com>
On 12.02.2016 16:52, Simon Glass wrote:
> Hi Hannes,
Hi Simon,
>
> On 11 February 2016 at 05:48, Hannes Schmelzer <hannes@schmelzer.or.at> wrote:
>> hi,
>>
>> i created some commit which i want to post into the mailing list usind
>> patman.py.
>>
>> I get following error, where i've no idea about the root cause ...
>>
>> ~/work/u-boot $ tools/patman/patman.py -n
>> Cleaned 1 patches
>> Traceback (most recent call last):
>> File "tools/patman/patman.py", line 158, in <module>
>> options.add_maintainers)
>> File "/home/schmelzerh/work/u-boot/tools/patman/series.py", line 222, in
>> MakeCcFile
>> raise_on_error=raise_on_error)
>> File "/home/schmelzerh/work/u-boot/tools/patman/gitutil.py", line 321, in
>> BuildEmailList
>> raw += LookupEmail(item, alias, raise_on_error=raise_on_error)
>> File "/home/schmelzerh/work/u-boot/tools/patman/gitutil.py", line 495, in
>> LookupEmail
>> raise ValueError, msg
>> ValueError: Alias 'gpio' not found
> Do you have a gpio: tag in your patch subject? If so, patman will try
> to email the patch to the 'gpio' alias. You can use -t to ignore
> invalid aliases.
Yes ... that works for me.
>
>> any suggestions ?
>>
>> many thanks and best regards,
>> Hannes
> Regards,
> Simonif
many thanks and best regards,
Hannes
prev parent reply other threads:[~2016-02-15 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 12:48 [U-Boot] trouble with patman Hannes Schmelzer
2016-02-12 15:52 ` Simon Glass
2016-02-15 6:39 ` Hannes Schmelzer [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=56C172AD.90405@schmelzer.or.at \
--to=hannes@schmelzer.or.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox