From: Christian Couder <christian.couder@gmail.com>
To: Shanthanu Rai <shanthanu.s.rai9@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [GSoC] Query regarding Microproject
Date: Fri, 20 Mar 2020 14:41:29 +0100 [thread overview]
Message-ID: <CAP8UFD2bgzvc2K2Sj4HSeXo16kB8D8se=+=Y7gp6FN+4Y3C1BQ@mail.gmail.com> (raw)
In-Reply-To: <CAGNOEmugZDWpvAHsOzmm_Fqo_Vj5GcC--GfTg3JHPm701HjBXA@mail.gmail.com>
Hi,
On Fri, Mar 20, 2020 at 7:39 AM Shanthanu Rai
<shanthanu.s.rai9@gmail.com> wrote:
>
> Hi, I am a 3rd Computer Science Undergrad at National Institute of
> Technology Surathkal, India. I wish to apply to git for GSoC.
>
> I am currently working on the microproject titled "Avoid pipes in git
> related commands in test scripts". I found 't/t9116-git-svn-log.sh' to
> have some commands wherein output of git is redirected to grep (using
> pipe). So shall I go ahead and make the required changes, i.e., redirect
> the output of git to a file and grep this file, in the relevant commands?
Yeah, sure.
In 't/t9116-git-svn-log.sh' it seems to me that some refactoring might
be needed too.
Best,
Christian.
next prev parent reply other threads:[~2020-03-20 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 6:37 [GSoC] Query regarding Microproject Shanthanu Rai
2020-03-20 13:41 ` Christian Couder [this message]
2020-03-20 16:27 ` Shanthanu
2020-03-21 9:49 ` Shanthanu
2020-03-23 19:31 ` Christian Couder
2020-03-25 13:51 ` Shanthanu
-- strict thread matches above, loose matches on Subject: below --
2019-03-05 8:05 [GSOC]:query regarding microproject Sushma Unnibhavi
2019-03-05 21:29 ` Thomas Gummerer
2019-03-04 5:26 [GSoC] Query " Umang Parmar
2019-03-04 7:41 ` Junio C Hamano
2019-03-04 7:52 ` Duy Nguyen
2019-03-04 9:05 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD2bgzvc2K2Sj4HSeXo16kB8D8se=+=Y7gp6FN+4Y3C1BQ@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=shanthanu.s.rai9@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).