Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul Koning <paul_koning@dell.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: can we avoid using contractions in GDB messages?
Date: Tue, 08 Mar 2011 04:54:00 -0000	[thread overview]
Message-ID: <20110308043522.GJ30306@adacore.com> (raw)
In-Reply-To: <C6938A0D-9D31-48BA-A62B-D79003BD02BC@dell.com>

> > My $0.02 -- I don't think there's anything wrong with contractions.
> > They're a part of standard English.
> 
> True.  But they are less familiar to those who are not native speakers.

OK, I think I might have been a little extreme, then, in my judgement
of contractions. I don't think it's question of familiarity, since
I remember learning about them fairly early on, if not in my first
English lesson. Interesting discussion, though :).

-- 
Joel


  reply	other threads:[~2011-03-08  4:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05  0:56 [commit] symfile.c (simple_overlay_update): Check for null return Michael Snyder
2011-03-07 11:07 ` can we avoid using contractions in GDB messages? (was: "[commit] symfile.c (simple_overlay_update): Check for null return.") Joel Brobecker
2011-03-07 11:30   ` can we avoid using contractions in GDB messages? Eli Zaretskii
2011-03-07 12:14     ` Joel Brobecker
2011-03-07 19:07   ` Michael Snyder
2011-03-07 19:19     ` Paul Koning
2011-03-08  4:54       ` Joel Brobecker [this message]
2011-03-07 21:58   ` can we avoid using contractions in GDB messages? (was: "[commit] symfile.c (simple_overlay_update): Check for null return.") Mike Frysinger

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=20110308043522.GJ30306@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=paul_koning@dell.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