From: Simon Hausmann <simon@lst.de>
To: "Matt McClure" <mlm@aya.yale.edu>
Cc: git@vger.kernel.org
Subject: Re: tests for git-p4
Date: Sun, 13 Jul 2008 14:26:03 +0200 [thread overview]
Message-ID: <200807131426.09688.simon@lst.de> (raw)
In-Reply-To: <e48c5e540807120524rabdcfa6vd91c16ef1b0f80a0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Saturday 12 July 2008 14:24:10 Matt McClure wrote:
> I'm planning to write a "p4-fast-export" that will facilitate using
> Bazaar on projects maintained in Perforce. I'd like to reuse code
> from git-p4 since it appears to have much of the functionality I want.
> In fact, the main reason I can't just use git-p4 today is that it
> does too much: it pushes the Perforce fast-export representation
> directly into Git. I'm going to work on covering the existing
> functionality in tests before I start modifying the code, and I could
> try to write those tests such that they'll be useful to the Git
> project as well.
>
> Would my tests be of interest to git-p4's authors? Is there any
> existing test framework for git-p4 that I missed?
There are currently no automated tests for git-p4. I would certainly be
interested, but I forsee difficulties testing the interaction with p4 in a
general way independent from a specific server setup.
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-13 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 12:24 tests for git-p4 Matt McClure
2008-07-12 14:36 ` Johannes Schindelin
2008-07-13 12:26 ` Simon Hausmann [this message]
2008-07-13 18:40 ` Matt McClure
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=200807131426.09688.simon@lst.de \
--to=simon@lst.de \
--cc=git@vger.kernel.org \
--cc=mlm@aya.yale.edu \
/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.