From: Julien Grall <julien.grall@arm.com>
To: "Wieczorkiewicz, Pawel" <wipawel@amazon.de>,
Ian Jackson <ian.jackson@citrix.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
KonradRzeszutek Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim \(Xen.org\)" <tim@xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
"Pohlack, Martin" <mpohlack@amazon.de>,
Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections
Date: Wed, 18 Sep 2019 12:19:22 +0100 [thread overview]
Message-ID: <f164b812-4b52-bf5b-d48a-57fcc1e824cf@arm.com> (raw)
In-Reply-To: <4134F5DE-6497-4F32-9A5F-866E4D6C0735@amazon.com>
Hi Pawel,
On 18/09/2019 11:44, Wieczorkiewicz, Pawel wrote:
>
>
>> On 18. Sep 2019, at 12:41, Ian Jackson <ian.jackson@citrix.com> wrote:
>>
>> Julien Grall writes ("Re: [PATCH] create-diff-object: more precisely identify .rodata sections"):
>>> On 18/09/2019 10:52, Wieczorkiewicz, Pawel wrote:
>>>> $ scripts/./add_maintainers.pl -d ~/git/livepatch-build-tools
>>>
>>> '-d' only tells you where the patches files are. The script will look up for the
>>> MAINTAINERS file in the current directory.
>>
>> Hmmm. I wonder if we could detect this situation somehow. This will
>> be a common user error I think.
>>
>
> I should have looked twice before sending the patch out. But, what would be very helpful for me
> is additional option to the add_maintainers.pl script like: -m ./MAINTAINERS
Well the filename will always be the same, so at best you will provide redundant
information.
However, it is not uncommon to have script that needs to apply on the current
directory. What would a new option add? Is it just avoid to do a "cd ..." before?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-18 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 7:35 [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections Pawel Wieczorkiewicz
2019-09-18 9:49 ` Jan Beulich
2019-09-18 9:52 ` Wieczorkiewicz, Pawel
2019-09-18 10:28 ` Julien Grall
2019-09-18 10:41 ` Ian Jackson
2019-09-18 10:44 ` Wieczorkiewicz, Pawel
2019-09-18 11:19 ` Julien Grall [this message]
2019-09-18 11:27 ` Wieczorkiewicz, Pawel
2019-09-18 11:35 ` Julien Grall
2019-09-18 15:23 ` Lars Kurth
2019-09-19 6:48 ` Wieczorkiewicz, Pawel
2019-09-18 11:50 ` Lars Kurth
2019-09-19 9:22 ` Julien Grall
2019-09-18 11:14 ` Julien Grall
2019-09-18 12:14 ` Lars Kurth
2019-09-19 9:30 ` Julien Grall
2019-11-05 15:37 [Xen-devel] [PATCH] create-diff-object: do not strip STN_UNDEF symbols from *.fixup Pawel Wieczorkiewicz
2019-11-05 15:37 ` [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections Pawel Wieczorkiewicz
2019-11-25 17:14 ` Ross Lagerwall
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=f164b812-4b52-bf5b-d48a-57fcc1e824cf@arm.com \
--to=julien.grall@arm.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=mpohlack@amazon.de \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wipawel@amazon.de \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.