From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/3] package/Makefile.in: add a way to don't force jobs in sub-make
Date: Tue, 17 Sep 2013 20:17:51 +0200 [thread overview]
Message-ID: <20130917201751.48fb34d3@skate> (raw)
In-Reply-To: <1379404753-3471-4-git-send-email-fabio.porcedda@gmail.com>
Dear Fabio Porcedda,
That's a minor nit, but "add a way to don't force jobs in sub-make"
isn't really correct english I blieve. "add away to not force the
number of jobs in sub-make" or something like that would be more
appropriate.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-17 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 7:59 [Buildroot] [PATCH v4 0/3] Fix for top-level parallel make part 1 Fabio Porcedda
2013-09-17 7:59 ` [Buildroot] [PATCH v4 1/3] package: add toolchain dependency to inner-generic-package Fabio Porcedda
2013-09-17 7:59 ` [Buildroot] [PATCH v4 2/3] pkg-generic: fix rules for top-level parallel make Fabio Porcedda
2013-09-17 18:23 ` Thomas Petazzoni
2013-09-19 6:53 ` Fabio Porcedda
2013-09-19 19:39 ` Thomas Petazzoni
2013-09-20 14:44 ` Fabio Porcedda
2013-09-20 16:39 ` Arnout Vandecappelle
2013-09-17 7:59 ` [Buildroot] [PATCH v4 3/3] package/Makefile.in: add a way to don't force jobs in sub-make Fabio Porcedda
2013-09-17 18:17 ` Thomas Petazzoni [this message]
2013-09-17 18:24 ` Ciarán Rehill
2013-09-19 6:35 ` Fabio Porcedda
2013-09-19 6:44 ` Thomas De Schampheleire
2013-09-19 6:59 ` Fabio Porcedda
2013-09-19 7:11 ` Thomas De Schampheleire
2013-09-20 14:57 ` Fabio Porcedda
2013-09-23 8:00 ` Fabio Porcedda
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=20130917201751.48fb34d3@skate \
--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.