From: Wincent Colaiuta <win@wincent.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Wincent Colaiuta <win@wincent.com>
Subject: [PATCH] Fix typo in 1.5.4 release notes
Date: Mon, 26 Nov 2007 09:34:48 +0100 [thread overview]
Message-ID: <1196066088-9558-1-git-send-email-win@wincent.com> (raw)
Signed-off-by: Wincent Colaiuta <win@wincent.com>
---
Documentation/RelNotes-1.5.4.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/RelNotes-1.5.4.txt b/Documentation/RelNotes-1.5.4.txt
index ff4d3d8..c9c5376 100644
--- a/Documentation/RelNotes-1.5.4.txt
+++ b/Documentation/RelNotes-1.5.4.txt
@@ -26,7 +26,7 @@ Updates since v1.5.3
* In git-rebase, when you decide not to replay a particular change
after the command stopped with a conflict, you can say "git-rebase
--skip" without first running "git reset --hard", as the command now
- run it for you.
+ runs it for you.
* git-remote knows --mirror mode.
--
1.5.3.6.950.g92b7b
reply other threads:[~2007-11-26 8:35 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=1196066088-9558-1-git-send-email-win@wincent.com \
--to=win@wincent.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).