All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] buildroot-test: failure reason regex update
Date: Fri, 1 Apr 2016 03:55:03 +0200	[thread overview]
Message-ID: <20160401035503.6f83bb24@free-electrons.com> (raw)
In-Reply-To: <1459468972-31420-2-git-send-email-matt@thewebers.ws>

Hello,

On Thu, 31 Mar 2016 19:02:52 -0500, Matt Weber wrote:
> - Sub-make required one additional line tailed

Really? Did you look at my previous review, where I showed the
different examples I could find, and showed that 3 lines were enough?

It's not like I care particularly whether we're tailing 3 or 4 lines,
it's more that I want to understand why in your scenario you would need
4 lines.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-01  1:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01  0:02 [Buildroot] [PATCH v2 1/2] buildroot-test: enable toolchains based on hostarch Matt Weber
2016-04-01  0:02 ` [Buildroot] [PATCH v2 2/2] buildroot-test: failure reason regex update Matt Weber
2016-04-01  1:55   ` Thomas Petazzoni [this message]
2016-04-01  2:37     ` Matthew Weber
2016-04-01  3:58       ` Thomas Petazzoni
2016-04-01  4:04         ` Matthew Weber
2016-04-01  4:21           ` Thomas Petazzoni
2016-09-06 20:04   ` Thomas Petazzoni
2016-09-06 21:20     ` Yann E. MORIN
2016-09-07  7:17     ` Thomas Petazzoni
2016-09-07  8:59       ` Yann E. MORIN
2016-04-21 21:05 ` [Buildroot] [PATCH v2 1/2] buildroot-test: enable toolchains based on hostarch Thomas Petazzoni

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=20160401035503.6f83bb24@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.