From: Dmitry Ivankov <divanorama@gmail.com>
To: git@vger.kernel.org
Cc: Dmitry Ivankov <divanorama@gmail.com>
Subject: [PATCH 2/3] Fix typo: existant->existent
Date: Thu, 2 Jun 2011 04:27:57 +0600 [thread overview]
Message-ID: <1306967278-1971-2-git-send-email-divanorama@gmail.com> (raw)
In-Reply-To: <1306967278-1971-1-git-send-email-divanorama@gmail.com>
Fix this typo in a comment.
---
git-gui/git-gui.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-gui/git-gui.sh b/git-gui/git-gui.sh
index fd6a43d..49efcee 100755
--- a/git-gui/git-gui.sh
+++ b/git-gui/git-gui.sh
@@ -1526,7 +1526,7 @@ proc run_prepare_commit_msg_hook {} {
# prepare-commit-msg requires PREPARE_COMMIT_MSG exist. From git-gui
# it will be .git/MERGE_MSG (merge), .git/SQUASH_MSG (squash), or an
- # empty file but existant file.
+ # empty file but existent file.
set fd_pcm [open [gitdir PREPARE_COMMIT_MSG] a]
--
1.7.3.4
next prev parent reply other threads:[~2011-06-01 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 22:27 [PATCH 1/3] Fix typo: existant->existent Dmitry Ivankov
2011-06-01 22:27 ` Dmitry Ivankov [this message]
2011-06-01 22:27 ` [PATCH 3/3] " Dmitry Ivankov
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=1306967278-1971-2-git-send-email-divanorama@gmail.com \
--to=divanorama@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).