From: Pete Wyckoff <pw@padd.com>
To: git@vger.kernel.org
Subject: [PATCH 00/11] git-p4: asciidoc documentation and fixes
Date: Sat, 17 Dec 2011 13:52:11 -0500 [thread overview]
Message-ID: <1324147942-21558-1-git-send-email-pw@padd.com> (raw)
This series starts with a revamp of the documentation for git-p4,
moving it into Documentation/ with the rest of the docs. Changes
from v1 of this patch address:
- review comments by Frans Klaver <fransklaver@gmail.com>
- review comments by Luke Diamand <luke@diamand.org>
- spellcheck
The other ten patches clarify the documentation, adding tests to
verify the current behavior of various git-p4 options. Three of
these also modify git-p4 itself.
Patch 6 adds code to catch two conflicting options.
Patch 10 fixes an obvious bug where both an option and a
variable existed, but were honored inconsistently.
Patch 11 catches an invocation problem and exits early with
an error message instead of waiting for an exception later.
Suggestions on how to rearrange these patches would be
welcome. I think the series is otherwise ready for testing
in next.
-- Pete
Pete Wyckoff (11):
git-p4: introduce asciidoc documentation
git-p4: test debug macro
git-p4: clone does not use --git-dir
git-p4: test cloning with two dirs, clarify doc
git-p4: document and test clone --branch
git-p4: honor --changesfile option and test
git-p4: document and test --import-local
git-p4: test --max-changes
git-p4: test --keep-path
git-p4: test and document --use-client-spec
git-p4: document and test submit options
Documentation/git-p4.txt | 480 ++++++++++++++++++++++++++++++++++++++++
contrib/fast-import/git-p4 | 32 +++-
contrib/fast-import/git-p4.txt | 302 -------------------------
t/lib-git-p4.sh | 27 +++
t/t9800-git-p4.sh | 60 +++++
t/t9806-options.sh | 170 ++++++++++++++
t/t9807-submit.sh | 54 +++++
7 files changed, 820 insertions(+), 305 deletions(-)
create mode 100644 Documentation/git-p4.txt
delete mode 100644 contrib/fast-import/git-p4.txt
create mode 100755 t/t9806-options.sh
--
1.7.8.258.g45cc3c
next reply other threads:[~2011-12-17 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 18:52 Pete Wyckoff [this message]
2011-12-17 18:52 ` [PATCH 01/11] git-p4: introduce asciidoc documentation Pete Wyckoff
2011-12-17 18:52 ` [PATCH 02/11] git-p4: test debug macro Pete Wyckoff
2011-12-17 22:43 ` Luke Diamand
2011-12-18 1:36 ` [PATCHv2 " Pete Wyckoff
2011-12-18 3:26 ` Jonathan Nieder
2011-12-18 13:50 ` Pete Wyckoff
2011-12-18 14:06 ` [PATCHv3 " Pete Wyckoff
2011-12-18 17:10 ` Luke Diamand
2011-12-18 21:48 ` Junio C Hamano
2011-12-20 1:35 ` Pete Wyckoff
2011-12-17 18:52 ` [PATCH 03/11] git-p4: clone does not use --git-dir Pete Wyckoff
2011-12-17 18:52 ` [PATCH 04/11] git-p4: test cloning with two dirs, clarify doc Pete Wyckoff
2011-12-17 18:52 ` [PATCH 05/11] git-p4: document and test clone --branch Pete Wyckoff
2011-12-17 18:52 ` [PATCH 06/11] git-p4: honor --changesfile option and test Pete Wyckoff
2011-12-17 18:52 ` [PATCH 07/11] git-p4: document and test --import-local Pete Wyckoff
2011-12-17 18:52 ` [PATCH 08/11] git-p4: test --max-changes Pete Wyckoff
2011-12-17 18:52 ` [PATCH 09/11] git-p4: test --keep-path Pete Wyckoff
2011-12-17 18:52 ` [PATCH 10/11] git-p4: test and document --use-client-spec Pete Wyckoff
2011-12-17 18:52 ` [PATCH 11/11] git-p4: document and test submit options Pete Wyckoff
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=1324147942-21558-1-git-send-email-pw@padd.com \
--to=pw@padd.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).