From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 18/20] python-service-identity: new package
Date: Fri, 19 Feb 2016 22:40:47 +0100 [thread overview]
Message-ID: <20160219224047.6276af21@free-electrons.com> (raw)
In-Reply-To: <1455188328-7595-1-git-send-email-mc5686@mclink.it>
Mauro,
On Thu, 11 Feb 2016 11:58:46 +0100, Mauro Condarelli wrote:
> Signed-off-by: Mauro Condarelli <mc5686@mclink.it>
Just a quick comment: it is really horrible for people
reviewing/applying your patches that you sent this patch separately
from the rest of the series. Now I have to manually figure out that
this patch labeled 18/20 in your v5 is in fact needed for patch 09/17
in your v4.
Please resend full series, so that the dependencies between patches
remain explicit. Or if you don't do that, resend the new iteration of a
patch as a reply to the previous patch and with the same sequence
number.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-19 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 10:58 [Buildroot] [PATCH v5 18/20] python-service-identity: new package Mauro Condarelli
2016-02-11 10:58 ` [Buildroot] [PATCH v5 19/20] python-autobahn: " Mauro Condarelli
2016-02-11 14:10 ` Yegor Yefremov
2016-02-20 14:05 ` Thomas Petazzoni
2016-02-20 15:53 ` Yegor Yefremov
2016-02-20 17:31 ` Thomas Petazzoni
2016-02-11 10:58 ` [Buildroot] [PATCH v5 20/20] python-crossbar: " Mauro Condarelli
2016-02-11 14:00 ` Yegor Yefremov
2016-02-20 14:38 ` Thomas Petazzoni
2016-02-20 15:46 ` Yegor Yefremov
2016-02-20 15:54 ` Thomas Petazzoni
2016-02-11 13:59 ` [Buildroot] [PATCH v5 18/20] python-service-identity: " Yegor Yefremov
2016-02-19 21:40 ` Thomas Petazzoni [this message]
2016-02-20 12:32 ` Mauro Condarelli
2016-02-20 12:57 ` Thomas Petazzoni
2016-02-19 22:18 ` 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=20160219224047.6276af21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox