All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Seyi Chamber <kuforiji98@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [Outreachy] Blog: Introducing myself as an intern working to convert unit test to use clar
Date: Sun, 22 Dec 2024 15:41:47 +0100	[thread overview]
Message-ID: <Z2glK5uJOX6ARFUa@pks.im> (raw)
In-Reply-To: <CAGedMtfDMj5P0T6x3soe3OUhRbpSw_-m1Vcm+rhDat1vvReK9w@mail.gmail.com>

On Sun, Dec 22, 2024 at 02:22:38PM +0100, Seyi Chamber wrote:
> On Sun, 22 Dec 2024 at 08:23, Patrick Steinhardt <ps@pks.im> wrote:
> >
> > On Fri, Dec 20, 2024 at 11:37:23AM +0100, Seyi Chamber wrote:
> > > Hello everyone,
> > >
> > > I just published a new blog post on unit test scripts I've selected
> > > and prioritized for initial conversion to clar. I would love for you
> > > to check it out and share your opinion!
> > >
> > > Find the link here:
> > > https://seyi-kuforiji-902b48.gitlab.io/posts/week-2-prioritizing-test-scripts
> >
> > Thanks for the blog post! The initial selection looks reasonable to me.
> > I was wondering whether it would make sense to evict "t-reftable-tree.c"
> > out of the first batch and then handle all reftable-related tests in a
> > single patch series. But we've got 9 of those, some of which are quite
> > complex, so that patch series would become quite large overall. So I
> > guess it's sensible to distribute the conversion of the reftable tests
> > across different patch series.
> >
> > Patrick
> 
> I suppose I could still make that work if that's your recommendation.
> I could divide the reftable-related tests into two sets and then treat
> them together. What do you think?

I'll leave it up to you, as there is no "right" or "wrong" in this
context.

Patrick

  reply	other threads:[~2024-12-22 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGedMtcSSkmQ2u9yYvKMiWnprWR2VZrbuoT9EX+U6nuxOWiEHw@mail.gmail.com>
2024-12-20 10:37 ` [Outreachy] Blog: Introducing myself as an intern working to convert unit test to use clar Seyi Chamber
2024-12-22  7:22   ` Patrick Steinhardt
2024-12-22 13:22     ` Seyi Chamber
2024-12-22 14:41       ` Patrick Steinhardt [this message]
2024-12-24  8:58 ` Seyi Chamber
2025-01-11  8:30   ` Seyi Chamber
2025-01-20 14:38     ` Seyi Chamber
2025-02-11  7:29       ` [Outreachy] Blog: Reflecting on tests converted to Clar (second batch) Seyi Chamber
2025-03-11 12:07       ` [Outreachy] Blog: Completion of My Outreachy Internship Seyi Chamber
2024-12-11 15:32 [Outreachy] Blog: Introducing myself as an intern working to convert unit test to use clar Seyi Chamber

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=Z2glK5uJOX6ARFUa@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=kuforiji98@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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.