From: Richard Fearn <richardfearn@gmail.com>
To: git@vger.kernel.org
Cc: Richard Fearn <richardfearn@gmail.com>
Subject: [PATCH] Fix spelling error in post-receive-email hook
Date: Sat, 13 Oct 2012 23:32:50 +0100 [thread overview]
Message-ID: <1350167570-11370-1-git-send-email-richardfearn@gmail.com> (raw)
Signed-off-by: Richard Fearn <richardfearn@gmail.com>
---
contrib/hooks/post-receive-email | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index 01af9df..b2171a0 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -403,7 +403,7 @@ generate_update_branch_email()
echo " \\"
echo " O -- O -- O ($oldrev)"
echo ""
- echo "The removed revisions are not necessarilly gone - if another reference"
+ echo "The removed revisions are not necessarily gone - if another reference"
echo "still refers to them they will stay in the repository."
rewind_only=1
else
--
1.7.11.7
next reply other threads:[~2012-10-13 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 22:32 Richard Fearn [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-13 22:14 [PATCH] Fix spelling error in post-receive-email hook Richard Fearn
2012-10-13 22:35 ` Richard Fearn
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=1350167570-11370-1-git-send-email-richardfearn@gmail.com \
--to=richardfearn@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).