From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] "info source" now includes producer string
Date: Tue, 06 Jan 2015 03:31:00 -0000 [thread overview]
Message-ID: <8361ck8tzx.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22SZSG0YYDd-Y3Sdt5M4v_j=31uCMwhVPTZuyR6Zdop5BQ@mail.gmail.com>
> Date: Mon, 5 Jan 2015 16:28:20 -0800
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
>
> >> +* The "info source" command now displays the producer string if it was
> >> + present in the debug info.
> >
> > I wonder whether we should replace "producer" with something less
> > abstract. Would "compilation command line" be accurate enough?
>
> The producer string can be anything, it's whatever the compiler
> decides, so I'm really hesitant to be specific here (and "command
> line" is too specific for me), because often it will be wrong.
We can always say "e.g." or "such as". That would at least describe
the most frequent use cases. We don't have to be 110% accurate here,
just clear enough to convey the intent.
next prev parent reply other threads:[~2015-01-06 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 20:41 Doug Evans
2015-01-05 20:50 ` Eli Zaretskii
2015-01-06 0:28 ` Doug Evans
2015-01-06 3:31 ` Eli Zaretskii [this message]
2015-01-31 22:29 ` Doug Evans
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=8361ck8tzx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).