From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch;rfa:doc] 5.2.50 on mainline
Date: Fri, 08 Oct 2004 09:47:00 -0000 [thread overview]
Message-ID: <01c4ad1b$Blat.v2.2.2$76b4d020@zahav.net.il> (raw)
In-Reply-To: <41646F7D.4070005@gnu.org> (message from Andrew Cagney on Wed, 06 Oct 2004 18:19:41 -0400)
> Date: Wed, 06 Oct 2004 18:19:41 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
>
> > Given the discussions about finding out MI versions, do we perhaps
> > want to tell vendors not to embed whitespace in their identifiers?
>
> I don't see it as a problem.
In my experience, whitespace make the automated parsing harder. But
if no one else sees this as a problem, I won't object.
> >>> ! @item all commits shall be covered by an assignment
> > Don't you need "should be covered"?
>
> Shall. It's a strict requirement.
Well, the text says ``guidelines'', not ``requirements''. Also, do we
really expect the reader of those to be fluent with the conventions of
MIL-STD-489 and its ilk? If not, ``shall'' sounds bad English in this
context, IMHO.
Otherwise, fine with me, thanks.
next prev parent reply other threads:[~2004-10-08 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 20:30 Andrew Cagney
2004-09-22 0:58 ` Joel Brobecker
2004-09-22 13:38 ` Andrew Cagney
2004-10-05 18:36 ` Andrew Cagney
2004-10-06 11:08 ` Eli Zaretskii
2004-10-06 22:20 ` Andrew Cagney
2004-10-08 9:47 ` Eli Zaretskii [this message]
2004-10-11 6:30 ` Andrew Cagney
2004-10-11 20:21 ` Eli Zaretskii
2004-10-12 19:15 ` Andrew Cagney
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='01c4ad1b$Blat.v2.2.2$76b4d020@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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