From: Frank Lichtenheld <frank@lichtenheld.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: [PATCH 0/5] cvsimport: Improve documentation
Date: Fri, 6 Apr 2007 23:52:38 +0200 [thread overview]
Message-ID: <11758963633237-git-send-email-frank@lichtenheld.de> (raw)
I played around with git-cvsimport the last days a bit and stumbled
upon a few inconsistencies in the documentation. This patch
series tries to fix them.
Documentation/git-cvsimport.txt | 79 ++++++++++++++++++++--------------------
git-cvsimport.perl | 17 ++++----
2 files changed, 50 insertions(+), 46 deletions(-)
next reply other threads:[~2007-04-06 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 21:52 Frank Lichtenheld [this message]
2007-04-06 21:52 ` [PATCH 1/5] cvsimport: sync usage lines with existing options Frank Lichtenheld
2007-04-06 21:52 ` [PATCH 2/5] cvsimport: Improve documentation of CVSROOT and CVS module determination Frank Lichtenheld
2007-04-06 21:52 ` [PATCH 3/5] cvsimport: Improve usage error reporting Frank Lichtenheld
2007-04-06 21:52 ` [PATCH 4/5] cvsimport: Reorder options in documentation for better understanding Frank Lichtenheld
2007-04-06 21:52 ` [PATCH 5/5] cvsimport: Improve formating consistency Frank Lichtenheld
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=11758963633237-git-send-email-frank@lichtenheld.de \
--to=frank@lichtenheld.de \
--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).