From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Dirk Suesserott <newsletter@dirk.my1.cc>
Subject: [PATCH] Documentation/git-request-pull: Fixed a typo ("send" -> "end")
Date: Wed, 9 Apr 2008 22:20:10 +0200 [thread overview]
Message-ID: <12077724101577-git-send-email-newsletter@dirk.my1.cc> (raw)
From: Dirk Suesserott <newsletter@dirk.my1.cc>
Signed-off-by: Dirk Suesserott <newsletter@dirk.my1.cc>
---
Documentation/git-request-pull.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-request-pull.txt b/Documentation/git-request-pull.txt
index 270df9b..9a14c04 100644
--- a/Documentation/git-request-pull.txt
+++ b/Documentation/git-request-pull.txt
@@ -24,7 +24,7 @@ OPTIONS
URL to include in the summary.
<end>::
- Commit to send at; defaults to HEAD.
+ Commit to end at; defaults to HEAD.
Author
------
--
1.5.4.2.1161.g1a6f0
reply other threads:[~2008-04-09 20:21 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=12077724101577-git-send-email-newsletter@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--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).