From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv3 13/11] Make relative-with-system-absolute the default
Date: Sat, 02 Feb 2013 18:07:00 -0000 [thread overview]
Message-ID: <20130202180658.GA16269@host2.jankratochvil.net> (raw)
In-Reply-To: <831ud2ioax.fsf@gnu.org>
On Wed, 30 Jan 2013 18:16:38 +0100, Eli Zaretskii wrote:
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -119,7 +119,9 @@ set filename-display basename|relative|absolute|relative-with-system-absolute
> > |basename-with-system-absolute
> > show filename-display
> > Control the way in which filenames is displayed.
> > - The default is "relative", which preserves previous behavior.
> > + Previous behavior was "relative".
> > + New default is "relative-with-system-absolute", which prints source filenames
> > + from files with present separate debug info in absolute form.
>
> I believe "present" should be removed from here.
I will remove it but it was present there to highlight it does not apply to
files with separated debug info where the separate debug info is currently not
installed. Although in such case no source filename is printed at all so it
is irrelevant whether it would be printed in absolute or relative form.
But maybe I am too biased into the internal details not interesting to casual
user.
Thanks,
Jan
next prev parent reply other threads:[~2013-02-02 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 22:11 [patchv2 " Jan Kratochvil
2013-01-30 7:49 ` [patchv3 " Jan Kratochvil
2013-01-30 17:17 ` Eli Zaretskii
2013-02-02 18:07 ` Jan Kratochvil [this message]
2013-02-02 18:27 ` Eli Zaretskii
2013-02-05 17:35 ` Doug Evans
2013-02-05 18:23 ` Jan Kratochvil
2013-02-06 16:02 ` Tom Tromey
2013-02-07 20:25 ` Doug Evans
2013-02-07 20:29 ` Jan Kratochvil
2013-02-15 19:58 ` [patch FYI not for commit] Attempt to properly relativize executable's filenames Jan Kratochvil
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=20130202180658.GA16269@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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