mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Rannaud <>
To: "SZEDER Gábor" <>
Cc: Junio C Hamano <>,
Subject: Re: [PATCH] t9300: wait for background fast-import process to die after killing it
Date: Thu, 19 Jul 2018 22:20:32 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Jul 19, 2018 at 3:26 PM, SZEDER Gábor <> wrote:
> But how do some of these messages end up on the test script's stderr,
> why don't we get them from all five tests, and why do they come from
> different file/line locations?

Thanks for the detailed explanation.

Signed-off-by: Eric Rannaud <>

  reply	other threads:[~2018-07-20  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 22:26 [PATCH] t9300: wait for background fast-import process to die after killing it SZEDER Gábor
2018-07-20  5:20 ` Eric Rannaud [this message]
2018-07-20 19:03 ` Elijah Newren

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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

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).