From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv3 12/11] New options {relative,basename}-with-system-absolute
Date: Fri, 01 Feb 2013 20:59:00 -0000 [thread overview]
Message-ID: <87y5f73g4h.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130130074820.GA15998@host2.jankratochvil.net> (Jan Kratochvil's message of "Wed, 30 Jan 2013 08:48:20 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> So a combination of absolute filenames for system component and relative
Jan> filenames for user binaries should be the best of both choices.
FWIW I think this makes sense.
Tom
prev parent reply other threads:[~2013-02-01 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 22:10 [patchv2 " Jan Kratochvil
2013-01-30 7:48 ` [patchv3 " Jan Kratochvil
2013-01-30 17:15 ` Eli Zaretskii
2013-01-30 18:30 ` Eli Zaretskii
2013-01-30 18:53 ` Jan Kratochvil
2013-01-30 20:11 ` Eli Zaretskii
2013-01-30 21:48 ` Doug Evans
2013-01-31 3:49 ` Eli Zaretskii
2013-01-31 18:07 ` Doug Evans
2013-01-31 18:54 ` Eli Zaretskii
2013-02-01 3:41 ` Doug Evans
2013-02-01 8:09 ` Eli Zaretskii
2013-02-02 18:12 ` Jan Kratochvil
2013-02-01 20:59 ` Tom Tromey [this message]
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=87y5f73g4h.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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