From: Calvin Wan <calvinwan@google.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] Add C TAP harness
Date: Thu, 27 Apr 2023 11:38:29 -0700 [thread overview]
Message-ID: <CAFySSZDSn1dETchvDjtFGaWZ7MrZeu_2iQZ9eR4Gd0+6SF-vUw@mail.gmail.com> (raw)
In-Reply-To: <20230427182918.GC3271@szeder.dev>
As an RFC, I didn't intend for this patch series to be taken as is.
The commits are intended as proof of concept to help readers visualize
what I am describing in the cover letter. If the general idea of
having a testing library for unit tests is acceptable, then I plan on
rerolling it as an actual series.
On Thu, Apr 27, 2023 at 11:29 AM SZEDER Gábor <szeder.dev@gmail.com> wrote:
>
> On Thu, Apr 27, 2023 at 05:50:06PM +0000, Calvin Wan wrote:
> > Introduces the C TAP harness from https://github.com/rra/c-tap-harness/
> >
> > There is also more complete documentation at
> > https://www.eyrie.org/~eagle/software/c-tap-harness/
> >
> > Signed-off-by: Calvin Wan <calvinwan@google.com>
>
> Why?
>
> Please remember that the justification of a change belongs to the
> commit message and that the contents of the cover letter will not be
> included in the history.
>
next prev parent reply other threads:[~2023-04-27 18:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 17:50 [RFC PATCH 0/2] add an external testing library for unit tests Calvin Wan
2023-04-27 17:50 ` [RFC PATCH 1/2] Add C TAP harness Calvin Wan
2023-04-27 18:29 ` SZEDER Gábor
2023-04-27 18:38 ` Calvin Wan [this message]
2023-04-27 20:15 ` Phillip Wood
2023-04-28 16:31 ` Calvin Wan
2023-05-02 15:46 ` Felipe Contreras
2023-05-10 15:46 ` Phillip Wood
2023-05-11 23:16 ` Glen Choo
2023-05-18 10:04 ` Phillip Wood
2023-06-21 15:57 ` Linus Arver
2023-06-26 13:15 ` Phillip Wood
2023-06-28 21:17 ` Linus Arver
2023-06-29 5:52 ` Oswald Buddenhagen
2023-06-30 9:48 ` Phillip Wood
2023-05-02 15:54 ` Felipe Contreras
2023-05-02 16:39 ` Ævar Arnfjörð Bjarmason
2023-05-02 18:11 ` Felipe Contreras
2023-05-02 16:34 ` Ævar Arnfjörð Bjarmason
2023-05-10 8:18 ` Phillip Wood
2023-04-27 17:50 ` [RFC PATCH 2/2] unit test: add basic example Calvin Wan
2023-04-27 18:47 ` Junio C Hamano
2023-05-02 15:58 ` Felipe Contreras
2023-04-27 18:39 ` [RFC PATCH 0/2] add an external testing library for unit tests Junio C Hamano
2023-04-27 18:46 ` Calvin Wan
2023-04-27 21:35 ` brian m. carlson
2023-05-02 4:18 ` Felipe Contreras
2023-05-02 13:52 ` Ævar Arnfjörð Bjarmason
2023-05-02 15:28 ` Felipe Contreras
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=CAFySSZDSn1dETchvDjtFGaWZ7MrZeu_2iQZ9eR4Gd0+6SF-vUw@mail.gmail.com \
--to=calvinwan@google.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).