From: Luke Diamand <luke@diamand.org>
To: Pete Wyckoff <pw@padd.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] git-p4 test cleanup, commit time change
Date: Sun, 31 Jul 2011 10:49:41 +0100 [thread overview]
Message-ID: <4E352535.4060804@diamand.org> (raw)
In-Reply-To: <20110731003557.GA4867@arf.padd.com>
On 31/07/11 01:35, Pete Wyckoff wrote:
> Here's a small patch series to clean up the git-p4 tests a bit,
> make them work on a 2-user eval p4d, and to fix a problem with
> the timestamp on the import commit.
>
> Luke, if you can take a look and ack these, I'd appreciate
> the review since I had to adjust your --preserveUser tests.
> And if you're looking at that one, might as well look at them
> all. :)
>
> I'd welcome review from anyone with interest, and will plan
> to submit these to Junio in a week or so.
Just looking at them now.
One thing though - are you sure the p4d demo license only allows 2
users? I've only ever used the demo p4d for testing and it seems to work
fine (just tried again with version P4D/LINUX26X86_64/2010.2/322263).
The web page says this:
"The free Perforce Server supports two users and five client workspaces,
or unlimited users and up to 1,000 files. Request a 45-day evaluation
license to support any number of users and unlimited files."
Which I assume means the test harness couldn't have more than 1000 files
and some unspecified number of client workspaces?
I've just created 4 users by hand with no obvious problems. I'm pretty
sure I'm not accidentally using the corporate server!
Confuzzled!
next prev parent reply other threads:[~2011-07-31 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 0:35 [PATCH 0/4] git-p4 test cleanup, commit time change Pete Wyckoff
2011-07-31 0:38 ` [PATCH 1/4] git-p4: use test_when_finished in tests Pete Wyckoff
2011-07-31 9:59 ` Luke Diamand
2011-07-31 0:39 ` [PATCH 2/4] git-p4: make tests work on p4d eval server Pete Wyckoff
2011-07-31 0:39 ` [PATCH 3/4] git-p4: one test missing config git-p4.skipSubmitEditCheck Pete Wyckoff
2011-07-31 10:01 ` Luke Diamand
2011-07-31 0:39 ` [PATCH 4/4] git-p4: commit time should be most recent p4 change time Pete Wyckoff
2011-07-31 10:14 ` Luke Diamand
2011-07-31 9:49 ` Luke Diamand [this message]
2011-07-31 13:42 ` [PATCH 0/4] git-p4 test cleanup, commit time change Pete Wyckoff
2011-07-31 16:01 ` Luke Diamand
2011-07-31 13:44 ` [PATCHv2 " Pete Wyckoff
2011-07-31 13:44 ` [PATCHv2 1/4] git-p4: use test_when_finished in tests Pete Wyckoff
2011-07-31 13:45 ` [PATCHv2 2/4] git-p4: add missing && in test Pete Wyckoff
2011-07-31 13:55 ` Luke Diamand
2011-07-31 13:45 ` [PATCHv2 3/4] git-p4: one test missing config git-p4.skipSubmitEditCheck Pete Wyckoff
2011-07-31 13:45 ` [PATCHv2 4/4] git-p4: commit time should be most recent p4 change time Pete Wyckoff
-- strict thread matches above, loose matches on Subject: below --
2011-08-07 13:31 [PATCH 0/4] git-p4 test cleanup, commit time change 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=4E352535.4060804@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=pw@padd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.