From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: ratmice@gmail.com, simon.marchi@polymtl.ca, tom@tromey.com,
orgads@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix python compatibility with old versions of GDB
Date: Tue, 13 Jun 2017 19:33:00 -0000 [thread overview]
Message-ID: <8360fz4r9h.fsf@gnu.org> (raw)
In-Reply-To: <87fuf3pw6t.fsf@pokyo> (message from Tom Tromey on Tue, 13 Jun 2017 12:41:14 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Simon Marchi <simon.marchi@polymtl.ca>, Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>, orgads@gmail.com, "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
> Date: Tue, 13 Jun 2017 12:41:14 -0600
>
> Matt> Is there any argument against appending version to the data-directory
> Matt> by default?
>
> Matt> e.g. gcc configures /usr/lib/gcc/triplet/version? I see a number of
> Matt> /usr/share/*/[0-9]\.* directories here.
>
> It's not harmful to do this, but it's also incomplete, because there's
> also the manual and the executable to consider.
The executable can be easily renamed, and there's no need to keep old
manuals, since the new one is mostly backward compatible (we rarely
make changes that change documented behavior).
next prev parent reply other threads:[~2017-06-13 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 17:48 Orgad Shaneh
2017-06-11 21:09 ` Simon Marchi
2017-06-12 4:31 ` Orgad Shaneh
2017-06-13 11:23 ` Simon Marchi
2017-06-13 12:12 ` Tom Tromey
2017-06-13 12:29 ` Phil Muldoon
2017-06-13 14:44 ` Eli Zaretskii
2017-06-13 17:29 ` Simon Marchi
2017-06-13 17:47 ` Matt Rice
2017-06-13 18:42 ` Tom Tromey
2017-06-13 19:33 ` Eli Zaretskii [this message]
2017-06-13 19:30 ` Eli Zaretskii
2017-06-13 12:53 ` Paul.Koning
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=8360fz4r9h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=orgads@gmail.com \
--cc=ratmice@gmail.com \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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