Re: [PATCH 0/2] microproject: avoid using pipes in test

From: Shubham Mishra <shivam828787@gmail.com>
Date: Feb 24, 2022, 05:22 UTC
Message-ID: <CAC316V5x54Ah566haa5wZ8zE=gkhYtziC+FVjXoBXn7xY_-WsQ@mail.gmail.com>
In-Reply-To: <CAP8UFD2wNSJmiohfAGrihm5sO_q4a6UpLMsVNAF5uWyuWt7R9Q@mail.gmail.com>

Show 9 quoted lines

> (Others have already rightly commented on many things, so I am only
> focusing on microproject related things.)
>
> As the subject of this cover letter starts with "microproject:" I
> would suggest taking a look (or maybe reading again) our page about
> microprojects: https://git.github.io/General-Microproject-Information/
>
> Please note that we ask that all related emails start with “[GSoC]” or
> “[Outreachy]” or something similar, not "microproject:".

Ack.

> > This is my first contribution that's why I am keeping diff short with an intention to understand the process instead of making impactful change in first attempt. Later, I will send more patches to fix the issue for other files.
>
> Please read the "Only ONE quality focused microproject per student"
> section of the above mentioned page.

here I mean in next patches, I will be fixing the same "Git on LHS of pipe" for other tests. I think that will be considered as the same microproject and I am still eligible to fix the same thing for other files?

Thanks, Shubham