From: Eli Zaretskii <eliz@gnu.org>
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com,
brobecker@adacore.com, palves@redhat.com, a3at.mail@gmail.com
Subject: Re: [PATCH v7] gdb: set filename-display shortpath support
Date: Wed, 11 Dec 2013 16:31:00 -0000 [thread overview]
Message-ID: <83lhzrwdr7.fsf@gnu.org> (raw)
In-Reply-To: <1386713214-30200-1-git-send-email-a3at.mail@gmail.com>
> From: Azat Khuzhin <a3at.mail@gmail.com>
> Cc: tromey@redhat.com,
> eliz@gnu.org,
> brobecker@adacore.com,
> palves@redhat.com,
> Azat Khuzhin <a3at.mail@gmail.com>
> Date: Wed, 11 Dec 2013 02:06:54 +0400
>
> V7: add NEWS and doc.
Thanks.
> +@item set filename-display shortpath
> +Display only non-common part of filenames and compilation directory.
I suggest an example here, because the description is somewhat
cryptic.
OK with that change.
next prev parent reply other threads:[~2013-12-11 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 22:07 Azat Khuzhin
2013-12-11 16:31 ` Eli Zaretskii [this message]
2013-12-11 18:48 ` Azat Khuzhin
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=83lhzrwdr7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=a3at.mail@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
/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