From: "Frank Ch. Eigler" <fche@redhat.com>
To: Serhei Makarov <me@serhei.io>
Cc: Keith Seitz <keiths@redhat.com>, Bunsen <bunsen@sourceware.org>
Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology
Date: Fri, 8 Apr 2022 21:56:45 -0400 [thread overview]
Message-ID: <20220409015645.GF23295@redhat.com> (raw)
In-Reply-To: <ceb2f84c-5c60-421a-bcf7-35bfea658b77@www.fastmail.com>
Hi -
> > Test suite. We've touched on this before, and I just want to reiterate:
> > THIS IS VITAL to prevent someone (realistically *me*) from breaking
> > your work. [...]
That should be straightforward with the new git/sqlite scheme too.
One can freeze a git repo for fixed testing, or one can edit one
under testsuite control. And one can easily query the resulting
datasets for expected values. Should be no problem at all for at
least the anlysis side of the house.
- FChE
next prev parent reply other threads:[~2022-04-09 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 18:59 Serhei Makarov
2022-03-07 19:03 ` Serhei Makarov
2022-04-07 16:57 ` Keith Seitz
2022-04-08 23:13 ` Serhei Makarov
2022-04-09 1:56 ` Frank Ch. Eigler [this message]
2022-04-09 2:22 ` Serhei Makarov
2022-04-09 2:26 ` Frank Ch. Eigler
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=20220409015645.GF23295@redhat.com \
--to=fche@redhat.com \
--cc=bunsen@sourceware.org \
--cc=keiths@redhat.com \
--cc=me@serhei.io \
/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).