From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/27] Documentation: Spelling fixes
Date: Sat, 03 Jun 2006 22:52:45 +0200 [thread overview]
Message-ID: <e5ssqp$mfh$1@sea.gmane.org> (raw)
In-Reply-To: 33723.2579863214$1149366476@news.gmane.org
Horst.H.von.Brand@inf.utfsm.cl wrote:
> From: Horst H. von Brand <vonbrand@inf.utfsm.cl>
>
> Result of a run of aspell(1) over the *.txt files in Documentation. Also
> fixed several other typoes.
Some of them (behavior vs. behaviour) are just the difference between
American nad British English. And couldn't do that all in _one_ patch?
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-06-03 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 20:26 [PATCH 0/27] Documentation: Spelling fixes Horst.H.von.Brand
2006-06-03 20:52 ` Jakub Narebski [this message]
2006-06-04 1:09 ` Junio C Hamano
2006-06-04 2:02 ` Horst von Brand
2006-06-04 17:59 ` Nikolai Weibull
2006-06-05 12:29 ` Andreas Ericsson
2006-06-05 16:48 ` Nikolai Weibull
2006-06-07 8:53 ` Andreas Ericsson
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='e5ssqp$mfh$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).