From: Patrick Steinhardt <ps@pks.im>
To: Seyi Chamber <kuforiji98@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH v2 Outreachy] t7011: ensure no whitespace after redirect
Date: Wed, 23 Oct 2024 11:55:31 +0200 [thread overview]
Message-ID: <ZxjIC5W4HprJqUxB@pks.im> (raw)
In-Reply-To: <CAGedMtdN8qRRALiYdCFso90ExGEm0zirnpLXuva_bc8ehsK+Xw@mail.gmail.com>
On Wed, Oct 23, 2024 at 08:24:18AM +0100, Seyi Chamber wrote:
> On Wed, 23 Oct 2024 at 06:00, Patrick Steinhardt <ps@pks.im> wrote:
> >
> > On Tue, Oct 22, 2024 at 06:11:17PM +0100, Seyi Chamber wrote:
> > > On Mon, 21 Oct 2024 at 20:58, Taylor Blau <me@ttaylorr.com> wrote:
> > > >
> > > > On Mon, Oct 21, 2024 at 06:17:06PM +0100, Seyi Chamber wrote:
> > > > > Yay!
> > > > >
> > > > > Thank you for the feedback @Patrick Steinhardt @Kristoffer Haugsbakk
> > > >
> > > > Thanks, all. Let's start merging this one down.
> > > >
> > > > Thanks,
> > > > Taylor
> > >
> > > Thanks, Taylor!
> > >
> > > I've also discovered that the test script t9101-git-svn-props.sh also
> > > requires the same update done in this patch.
> > > Is this test script currently being worked on? @Patrick Steinhardt
> >
> > Not that I'd know of. I typically double check via lore by searching for
> > the relevant subsystem [1]. This only surfaces your mail and the Meson
> > patch series, so at least nobody else has communicated intent to work on
> > it.
> >
> > Patrick
> >
> > [1]: https://lore.kernel.org/git/?q=t9101
>
> Thanks, Patrick.
>
> In the future, would you prefer I still run it by you before working
> on a test script,
> or should I apply the same strategy you mentioned in your reply?
There's no need to run it by anybody, so please feel free to use the
same strategy.
Patrick
prev parent reply other threads:[~2024-10-23 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 16:34 [PATCH v2 Outreachy] t7011: ensure no whitespace after redirect Seyi Kuforiji
2024-10-19 17:54 ` Kristoffer Haugsbakk
2024-10-21 12:03 ` Patrick Steinhardt
2024-10-21 17:17 ` Seyi Chamber
2024-10-21 19:58 ` Taylor Blau
2024-10-22 17:11 ` Seyi Chamber
2024-10-23 5:00 ` Patrick Steinhardt
2024-10-23 7:24 ` Seyi Chamber
2024-10-23 9:55 ` Patrick Steinhardt [this message]
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=ZxjIC5W4HprJqUxB@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=kuforiji98@gmail.com \
--cc=me@ttaylorr.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 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 NNTP newsgroup(s).