All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 2/2] perl-xml-parser: new package
Date: Mon, 13 Aug 2018 23:05:17 +0200	[thread overview]
Message-ID: <20180813230517.189c07a5@windsurf> (raw)
In-Reply-To: <20180813175645.11088-3-chrismcc@gmail.com>

Hello,

On Mon, 13 Aug 2018 10:56:45 -0700, Christopher McCrory wrote:
> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>

This seems to be a partial patch.

Your patch series seems a bit messed up. You have sent:

  RFC PATCH 0/2
  RFC PATCH 1/2
  RFC PATCH 2/2 (this patch, which is partial)
  RFC PATCH 4/4

Could you fix this up and send a proper patch series ? If you're not
familiar yet with git send-email, I would suggest that you send your
patch series to yourself first, to make sure everything is correct,
before sending them to the Buildroot mailing list.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-13 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 17:56 [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories Christopher McCrory
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 1/2] perl-template-toolkit: new package Christopher McCrory
2018-08-14  4:21   ` François Perrad
2018-08-15 12:03     ` Christopher McCrory
2018-08-15 18:06       ` François Perrad
2018-08-15 20:24         ` Christopher McCrory
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 2/2] perl-xml-parser: " Christopher McCrory
2018-08-13 21:05   ` Thomas Petazzoni [this message]
2018-08-13 21:54     ` Christopher McCrory
2018-08-13 21:03 ` [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories 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=20180813230517.189c07a5@windsurf \
    --to=thomas.petazzoni@bootlin.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.