From: "Michael W. Olson" <mwolson@gnu.org>
To: git@vger.kernel.org
Cc: "Michael W. Olson" <mwolson@gnu.org>
Subject: [PATCH] Documentation/git-cvsexportcommit.txt: s/mgs/msg/ in example
Date: Tue, 30 Oct 2007 09:53:47 -0400 [thread overview]
Message-ID: <1193752427-21280-1-git-send-email-mwolson@gnu.org> (raw)
---
Documentation/git-cvsexportcommit.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-cvsexportcommit.txt b/Documentation/git-cvsexportcommit.txt
index 4c8d1e6..c3922f9 100644
--- a/Documentation/git-cvsexportcommit.txt
+++ b/Documentation/git-cvsexportcommit.txt
@@ -73,7 +73,7 @@ Merge one patch into CVS::
$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git-cvsexportcommit -v <commit-sha1>
-$ cvs commit -F .mgs <files>
+$ cvs commit -F .msg <files>
------------
Merge pending patches into CVS automatically -- only if you really know what you are doing::
--
1.5.3.4
next reply other threads:[~2007-10-30 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 13:53 Michael W. Olson [this message]
2007-10-30 18:39 ` [PATCH] Documentation/git-cvsexportcommit.txt: s/mgs/msg/ in example Junio C Hamano
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=1193752427-21280-1-git-send-email-mwolson@gnu.org \
--to=mwolson@gnu.org \
--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).