From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Pranit Bauva <pranit.bauva@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Christian Couder <christian.couder@gmail.com>,
Git List <git@vger.kernel.org>,
Stefan Beller <sbeller@google.com>,
Lars Schneider <larsxschneider@gmail.com>,
Jeff King <peff@peff.net>, Troy Moure <troy.moure@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Kevin Daudt <me@ikke.info>, Philip Oakley <philipoakley@iee.org>
Subject: Re: GSoC Project | Improvise git bisect
Date: Sun, 20 Mar 2016 19:08:15 +0100 [thread overview]
Message-ID: <vpqoaa9c99s.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAFZEwPMEDnzv3mLpULOY=7CQZgULx5QsAb_4Pz40iJWzt9HRGg@mail.gmail.com> (Pranit Bauva's message of "Sun, 20 Mar 2016 21:56:54 +0530")
Pranit Bauva <pranit.bauva@gmail.com> writes:
> When I am writing
> functions, I am thinking to make some tests which will be copied
> contents of t/t6030-bisect-porcelain.sh with s/bisect/bisect--helper/g
> uncommenting tests as I implement more functions.
I don't think you need that. When you write a new function, you are
removing pieces of shell and adding pieces of C as replacement. If the
testsuite is complete, it covers the shell implementation today and will
cover the C implementation when it replaces the shell.
The existing tests should be usable without modification.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-03-20 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 9:33 GSoC Project | Improvise git bisect Pranit Bauva
2016-03-19 12:48 ` Matthieu Moy
2016-03-19 16:14 ` Christian Couder
2016-03-19 16:49 ` Pranit Bauva
2016-03-19 22:05 ` Stefan Beller
2016-03-20 8:10 ` Pranit Bauva
2016-03-20 11:35 ` Pranit Bauva
2016-03-20 13:24 ` Matthieu Moy
2016-03-20 13:25 ` Christian Couder
2016-03-20 15:31 ` Johannes Schindelin
2016-03-20 16:26 ` Pranit Bauva
2016-03-20 18:08 ` Matthieu Moy [this message]
2016-03-21 7:18 ` Johannes Schindelin
2016-03-21 7:29 ` Pranit Bauva
2016-03-21 17:53 ` Christian Couder
2016-03-21 18:13 ` Pranit Bauva
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=vpqoaa9c99s.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=me@ikke.info \
--cc=peff@peff.net \
--cc=philipoakley@iee.org \
--cc=pranit.bauva@gmail.com \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.com \
--cc=troy.moure@gmail.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.