From: Mark Wielaard <mark@klomp.org>
To: tromey@redhat.com
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: typos
Date: Sat, 01 Mar 2008 22:49:00 -0000 [thread overview]
Message-ID: <1204411706.3279.59.camel@localhost.localdomain> (raw)
In-Reply-To: <m3r6euf8a3.fsf@fleche.redhat.com>
Hi Tom,
On Sat, 2008-03-01 at 14:23 -0700, Tom Tromey wrote:
> This fixes a couple typos I happened across.
> There are actually a lot of inconsistencies in the in-program help,
> but I didn't feel like trying to clean that up, so I just filed a bug.
Thanks for the patch and for filing the bug.
http://sourceware.org/bugzilla/show_bug.cgi?id=5810
> frysk-core/frysk/hpd/ChangeLog:
> 2008-03-01 Tom Tromey <tromey@redhat.com>
>
> * RunCommand.java (RunCommand): Fix typo.
> * LoadCommand.java (LoadCommand): Add missing spaces.
Pushed.
Mark
prev parent reply other threads:[~2008-03-01 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 22:14 typos Tom Tromey
2008-03-01 22:49 ` Mark Wielaard [this message]
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=1204411706.3279.59.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).