From: "Bjørn Lindeijer" <bjorn@lindeijer.nl>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] Spelling fix in release notes
Date: Sat, 6 Dec 2008 23:00:56 +0100 [thread overview]
Message-ID: <853f61c50812061400n46904efcl534dd7c6353d7ca4@mail.gmail.com> (raw)
Signed-off-by: Bjørn Lindeijer <bjorn@lindeijer.nl>
---
Documentation/RelNotes-1.6.1.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/RelNotes-1.6.1.txt b/Documentation/RelNotes-1.6.1.txt
index 9f5c0b5..9593075 100644
--- a/Documentation/RelNotes-1.6.1.txt
+++ b/Documentation/RelNotes-1.6.1.txt
@@ -70,7 +70,7 @@ on.
subsequent "git diff" will show a diff as if they are creation events.
* "git add" gained a built-in synonym for people who want to say "stage
- changes" instead of "add contents the the staging area" which amounts
+ changes" instead of "add contents to the staging area" which amounts
to the same thing.
* "git apply" learned --include=paths option, similar to the existing
--
1.6.1.rc1.57.g71562
reply other threads:[~2008-12-06 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=853f61c50812061400n46904efcl534dd7c6353d7ca4@mail.gmail.com \
--to=bjorn@lindeijer.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).