From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86: print relevant (tail) part of filename for warnings and crashes
Date: Wed, 16 Oct 2013 16:52:24 +0100 [thread overview]
Message-ID: <CE8474C8.398C2%keir.xen@gmail.com> (raw)
In-Reply-To: <525ECC1702000078000FB8D7@nat28.tlf.novell.com>
On 16/10/2013 16:25, "Jan Beulich" <JBeulich@suse.com> wrote:
> In particular when the origin construct is in a header file (and
> hence the file name is an absolute path instead of just the file name
> portion) the information can otherwise become rather useless when the
> build tree isn't sitting relatively close to the file system root.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
next prev parent reply other threads:[~2013-10-16 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 15:25 [PATCH] x86: print relevant (tail) part of filename for warnings and crashes Jan Beulich
2013-10-16 15:52 ` Keir Fraser [this message]
2013-10-16 15:57 ` Andrew Cooper
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=CE8474C8.398C2%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--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 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).