From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Pratik Karki <predatoramigo@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [GSoC][PATCH v3] test: avoid pipes in git related commands for test
Date: Wed, 21 Mar 2018 14:58:54 -0400 [thread overview]
Message-ID: <CAPig+cRnO6e5B=mYAfkt7bdgit2uOJk1a+CAahQ2+uRRbPAObQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqo9jhpadh.fsf@gitster-ct.c.googlers.com>
On Wed, Mar 21, 2018 at 2:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Pratik Karki <predatoramigo@gmail.com> writes:
>> Avoid using pipes downstream of Git commands since the exit
>> codes of commands upstream of pipes get swallowed, thus potentially hiding
>> failure of those commands. Instead, capture Git command output to a file and
>> apply the downstream command(s) to that file.
>
> Please do not indent the body of the log message by one space.
One other issue I forgot to mention is that the commit message in v3
started getting too wide again[1]; it was fine in v2. Pratik, try to
keep the commit message wrapped to about 70-72 characters or so.
[1]: https://public-inbox.org/git/CAPig+cRPzyw525ODC4=-E7w=zbpbhVN2eqxSYDSLij5wfW8S_A@mail.gmail.com/
next prev parent reply other threads:[~2018-03-21 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 20:19 [GSoC] [PATCH] test: avoid pipes in git related commands for test suite Pratik Karki
2018-03-14 7:30 ` Eric Sunshine
2018-03-14 9:57 ` Ævar Arnfjörð Bjarmason
2018-03-14 18:22 ` Eric Sunshine
2018-03-15 17:04 ` Junio C Hamano
2018-03-19 17:32 ` [GSoC][PATCH] " Pratik Karki
2018-03-21 11:02 ` Eric Sunshine
2018-03-21 15:23 ` [GSoC][PATCH v3] test: avoid pipes in git related commands for test Pratik Karki
2018-03-21 18:11 ` Junio C Hamano
2018-03-21 18:45 ` Eric Sunshine
2018-03-21 18:58 ` Eric Sunshine [this message]
2018-03-23 15:01 ` [GSoC][PATCH v4] " Pratik Karki
2018-03-25 8:37 ` Eric Sunshine
2018-03-27 17:31 ` [GSoC][PATCH v5] " Pratik Karki
2018-03-30 21:45 ` Eric Sunshine
2018-03-30 22:08 ` Junio C Hamano
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='CAPig+cRnO6e5B=mYAfkt7bdgit2uOJk1a+CAahQ2+uRRbPAObQ@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=predatoramigo@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).