From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: trivial: typo
Date: Thu, 5 Jan 2006 12:44:59 +0100 [thread overview]
Message-ID: <81b0412b0601050344m51699b33y529efeb20f357b0@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 49 bytes --]
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
[-- Attachment #2: 0003-typo.txt --]
[-- Type: text/plain, Size: 624 bytes --]
Subject: [PATCH] typo
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---
git-commit.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
870dff0c4ef444c084415d55e40e17aab16a3e68
diff --git a/git-commit.sh b/git-commit.sh
index 7e39c10..82d743b 100755
--- a/git-commit.sh
+++ b/git-commit.sh
@@ -148,7 +148,7 @@ esac
if [ -f "$GIT_DIR/MERGE_HEAD" ]; then
echo "#"
- echo "# It looks like your may be committing a MERGE."
+ echo "# It looks like you may be committing a MERGE."
echo "# If this is not correct, please remove the file"
echo "# $GIT_DIR/MERGE_HEAD"
echo "# and try again"
--
1.0.GIT
reply other threads:[~2006-01-05 11:45 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=81b0412b0601050344m51699b33y529efeb20f357b0@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).