From: Pete Wyckoff <pw@padd.com>
To: git@vger.kernel.org
Cc: Gary Gibbons <ggibbons@perforce.com>
Subject: [PATCH 0/5] git-p4: view spec review fixes
Date: Wed, 11 Jan 2012 18:31:05 -0500 [thread overview]
Message-ID: <1326324670-15967-1-git-send-email-pw@padd.com> (raw)
I received some helpful review comments offline regarding the
series recently merged into master (8cbfc11
(Merge branch 'pw/p4-view-updates', 2012-01-06)).
It would be nice to see these go into 1.7.9 as well.
Even though they belong there logically, they are
minor fixes, and not critical.
I added a bunch of new tests documenting further problems,
but will not fix those here as the changes will be more
invasive.
Thanks,
Pete Wyckoff (5):
git-p4: only a single ... wildcard is supported
git-p4: fix verbose comment typo
git-p4: clarify comment
git-p4: adjust test to adhere to stricter useClientSpec
git-p4: add tests demonstrating spec overlay ambiguities
Documentation/git-p4.txt | 5 +
contrib/fast-import/git-p4 | 9 +-
t/t9806-git-p4-options.sh | 4 +-
t/t9809-git-p4-client-view.sh | 395 ++++++++++++++++++++++++++++++++++++++++-
4 files changed, 406 insertions(+), 7 deletions(-)
--
1.7.8.1.409.g3e338.dirty
next reply other threads:[~2012-01-11 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 23:31 Pete Wyckoff [this message]
2012-01-11 23:31 ` [PATCH 1/5] git-p4: only a single ... wildcard is supported Pete Wyckoff
2012-01-11 23:31 ` [PATCH 2/5] git-p4: fix verbose comment typo Pete Wyckoff
2012-01-11 23:31 ` [PATCH 3/5] git-p4: clarify comment Pete Wyckoff
2012-01-11 23:31 ` [PATCH 4/5] git-p4: adjust test to adhere to stricter useClientSpec Pete Wyckoff
2012-01-11 23:31 ` [PATCH 5/5] git-p4: add tests demonstrating spec overlay ambiguities 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=1326324670-15967-1-git-send-email-pw@padd.com \
--to=pw@padd.com \
--cc=ggibbons@perforce.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).