Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org, brobecker@adacore.com,
	       palves@redhat.com
Subject: Re: [PATCH v5] gdb: set filename-display shortpath support
Date: Tue, 10 Dec 2013 21:04:00 -0000	[thread overview]
Message-ID: <87wqjc4dur.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1386624043-11077-1-git-send-email-a3at.mail@gmail.com> (Azat	Khuzhin's message of "Tue, 10 Dec 2013 01:20:43 +0400")

>>>>> "Azat" == Azat Khuzhin <a3at.mail@gmail.com> writes:

Azat> Display only non-common part of filename and compilation directory
Azat> This will be useful for projects that use separate build directory
Azat> inside project (like build/cmake and others).

Thanks for doing this.

Azat> 2013-12-00  Azat Khuzhin  <a3at.mail@gmail.com>
Azat> 	* source.h (symtab_to_shortpath): Add it.
Azat> 	* source.c (filename_display): Add shortpath display.
Azat> 	* (symtab_to_filename_for_display): Use symtab_to_shortpath.

That final line doesn't need the "* ".
Silly ChangeLogs.

I think this patch needs at least a documentation patch and a NEWS
entry.

A test case would be nice, an addition to an existing test would be
sufficient.

Do you have copyright assignment paperwork in place?
If not then please contact me off-list so I can get you started.

Azat> +/* Returns only non-common part of filename and compilation directory. */
Azat> +extern const char *symtab_to_shortpath(struct symtab *symtab);

Space before the open paren here.

Tom


  reply	other threads:[~2013-12-10 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 21:21 Azat Khuzhin
2013-12-10 21:04 ` Tom Tromey [this message]
2013-12-10 21:23   ` Azat Khuzhin
2013-12-10 21:50     ` Tom Tromey

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=87wqjc4dur.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=a3at.mail@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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