Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obish/6.2] GNU/Linux usage
Date: Sat, 17 Jul 2004 14:25:00 -0000	[thread overview]
Message-ID: <20040717142435.GA28962@nevyn.them.org> (raw)
In-Reply-To: <40F934DE.30803@gnu.org>

On Sat, Jul 17, 2004 at 10:17:02AM -0400, Andrew Cagney wrote:
> -         Linux Standards Base says that programs that use 'long
> +         Linux[sic] Standards Base says that programs that use 'long
>           double' on PPC GNU/Linux are non-conformant.  */
>        set_gdbarch_long_double_bit (gdbarch, 8 * TARGET_CHAR_BIT);

Er, is that really necessary?  It's a workgroup named "Linux Standards
Base" and even has the trademark for "LSB".  I'd be annoyed if a [sic]
appeared in the middle of my company name, for sure.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-07-17 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17 14:17 Andrew Cagney
2004-07-17 14:25 ` Daniel Jacobowitz [this message]
2004-07-26 18:37   ` Andrew Cagney
2004-07-26 19:00     ` Daniel Jacobowitz
2004-07-28 18:57       ` Jim Blandy

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=20040717142435.GA28962@nevyn.them.org \
    --to=drow@false.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