From: Sverre Rabbelier <srabbelier@gmail.com>
To: Guanqun Lu <guanqun.lu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] fix typo in Documentation
Date: Wed, 4 Feb 2009 06:30:11 +0100 [thread overview]
Message-ID: <bd6139dc0902032130k47551f1cle52ae286bd539e5d@mail.gmail.com> (raw)
In-Reply-To: <1233781241-721-1-git-send-email-guanqun.lu@gmail.com>
Heya,
On Wed, Feb 4, 2009 at 22:00, Guanqun Lu <guanqun.lu@gmail.com> wrote:
> -However, it it totally safe to modify anything in the string pointed by
> +However, it is totally safe to modify anything in the string pointed by
To prevent someone else from staring at this for a minute, "it it" was
replaced by "it is".
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-02-04 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 21:00 [PATCH 1/2] fix typo in Documentation Guanqun Lu
2009-02-04 5:30 ` Sverre Rabbelier [this message]
2009-02-04 9:26 ` Jakub Narebski
2009-02-05 6:27 ` Guanqun Lu
2009-02-04 21:00 ` [PATCH 2/2] add test-dump-cache-tree in Makefile Guanqun Lu
2009-02-04 7:46 ` Junio C Hamano
2009-02-04 9:31 ` Jakub Narebski
2009-02-06 13:43 ` [PATCH 1/2] fix typo in Documentation Mikael Magnusson
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=bd6139dc0902032130k47551f1cle52ae286bd539e5d@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=guanqun.lu@gmail.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 NNTP newsgroup(s).