All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Lafeldt <mathias.lafeldt@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Sharness - Test library derived from Git
Date: Fri, 20 Jul 2012 12:18:51 +0200	[thread overview]
Message-ID: <CAMFa-2gRWRKgj140i1q9iux=eC6nWxfdUPPhb42xAG1Gr7e4vA@mail.gmail.com> (raw)
In-Reply-To: <CACBZZX6QZACjkFPEsNgAkKgnkZHDsCOEAm=-9rs=PLiSfgsXBw@mail.gmail.com>

On Tue, Jul 17, 2012 at 8:31 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> Nice, I thought about doing something like this myself but never had the time.

Thanks. Took quite some time to take out the Git-specific
functionality. And there's still a lot of room for improvement.

> Perhaps to avoid duplication we could move to this and keep
> Git-specific function in some other file.

That would be fantastic! From a technical point of view, it would make
a lot of sense to join forces here.

How do you think would Sharness fit into the Git project? Is adding it
as an external dependency an option?

Let's share some ideas before getting to it.

> Do you think that would be sensible, and would you be willing to
> submit patches for that?

While I haven't touched the names of the test functions, I renamed
most of the global shell variables, e.g. GIT_TEST_OPTS to TEST_OPTS
and TEST_DIRECTORY to SHARNESS_TEST_DIRECTORY. That might be a (minor)
problem.

As for the patches: absolutely. I'd really love to give something back to Git.

-Mathias

  reply	other threads:[~2012-07-20 10:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  8:06 [ANNOUNCE] Sharness - Test library derived from Git Mathias Lafeldt
2012-07-17 18:31 ` Ævar Arnfjörð Bjarmason
2012-07-20 10:18   ` Mathias Lafeldt [this message]
2012-07-20 11:45     ` Matthieu Moy
2012-07-20 21:11       ` dag

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='CAMFa-2gRWRKgj140i1q9iux=eC6nWxfdUPPhb42xAG1Gr7e4vA@mail.gmail.com' \
    --to=mathias.lafeldt@gmail.com \
    --cc=avarab@gmail.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 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.