From: Pedro Alves <palves@redhat.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
gdb-patches@sourceware.org, "Doug Evans" <xdje42@gmail.com>
Subject: Re: [PATCH] guile: Compile and install Scheme files.
Date: Tue, 15 Jul 2014 09:53:00 -0000 [thread overview]
Message-ID: <53C4F7A7.9070003@redhat.com> (raw)
In-Reply-To: <87bntnl0wt.fsf@gnu.org>
Hi Ludovic,
Can we have a a comment somewhere (either in the sources, or in
the commit log), of _why_ we do this? E.g., is this for
performance, or for something else? When it is safe? Etc.
These are things I'm sure you've considered, and having them
written them would potentially save poor-future-gdb-hacker
from having to wonder/re-consider them down-the-line. Thanks! :-)
--
Pedro Alves
next prev parent reply other threads:[~2014-07-15 9:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 21:35 Ludovic Courtès
2014-07-12 12:37 ` Doug Evans
2014-07-15 9:53 ` Pedro Alves [this message]
2014-07-19 14:57 ` Ludovic Courtès
2014-07-19 15:26 ` Doug Evans
2014-07-19 16:14 ` Eli Zaretskii
2014-07-19 17:11 ` Doug Evans
2014-07-19 21:40 ` Eli Zaretskii
2014-07-19 17:06 ` Ludovic Courtès
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=53C4F7A7.9070003@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=xdje42@gmail.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