From: Ramkumar Ramachandra <artagnon@gmail.com>
To: 乙酸鋰 <ch3cooli@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] relnotes: fix spelling error in 1.8.4.txt
Date: Mon, 3 Jun 2013 15:38:24 +0530 [thread overview]
Message-ID: <1370254104-16358-1-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <CAHtLG6SGF=D-_gz47qAfhvkZHPU3-Ucj-cM_aF8BhTsE1mo2sg@mail.gmail.com>
From: 乙酸鋰 <ch3cooli@gmail.com>
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
乙酸鋰: please read Documentation/SubmittingPatches and submit a
patch yourself next time. I've done it for you this time as an
example.
Junio: please (add-hook 'text-mode-hook 'flyspell-mode) to your
.emacs to catch this early.
Documentation/RelNotes/1.8.4.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/RelNotes/1.8.4.txt b/Documentation/RelNotes/1.8.4.txt
index 14835d1..0e08bf4 100644
--- a/Documentation/RelNotes/1.8.4.txt
+++ b/Documentation/RelNotes/1.8.4.txt
@@ -36,7 +36,7 @@ UI, Workflows & Features
did not update "refs/remotes/origin/master"; this was an early
design decision to keep the update of remote tracking branches
predictable, but in practice it turns out that people find it more
- convenient to opportunisticly update them whenever we have a
+ convenient to opportunistically update them whenever we have a
chance, and we have been updating them when we run "git push" which
already breaks the original "predictability" anyway.
--
1.8.3.114.gcd03571
next prev parent reply other threads:[~2013-06-03 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 1:36 Typo in Documentation/RelNotes/1.8.4.txt 乙酸鋰
2013-06-03 10:08 ` Ramkumar Ramachandra [this message]
2013-06-03 11:55 ` Drew Northup
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=1370254104-16358-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=ch3cooli@gmail.com \
--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).