From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Fix typos in technical documentation.
Date: Mon, 01 Feb 2010 12:55:52 -0800 [thread overview]
Message-ID: <7vaavsvfon.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpqsk9m5nt1.fsf@bauges.imag.fr> (Matthieu Moy's message of "Sun\, 31 Jan 2010 15\:52\:42 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
>
>> Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
>> ---
>>
>> Hi there,
>>
>> stumbled upon a couple of these, then grepped for the rest
>> in Documentation/.
>
> Nice catches!
Yeah, applied. Thanks.
prev parent reply other threads:[~2010-02-01 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 13:24 [PATCH] Fix typos in technical documentation Ralf Wildenhues
2010-01-31 14:52 ` Matthieu Moy
2010-02-01 20:55 ` Junio C Hamano [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=7vaavsvfon.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
/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).