Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] perl-xml-libxml: new package
Date: Tue, 24 Jun 2014 07:29:33 +0200	[thread overview]
Message-ID: <53A90CBD.6000904@mind.be> (raw)
In-Reply-To: <1403547286-8858-3-git-send-email-francois.perrad@gadz.org>

On 23/06/14 20:14, Francois Perrad wrote:
> and its CPAN dependencies

 This should be split up into four separate patch, one per package. It's quite
easy to do that with git:

git reset master
git add package/perl-xml-namespacesupport
git add -p package/Config.in

and select 'e' to edit the patch, and remove all + lines except the one for
perl-xml-namespacesupport.


 Otherwise, it all looks good. Seems the scancpan script is working well! So
when you resubmit as separate patches, you can add my Reviewed-by tag.

 Regards,
 Arnout


> 
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
>  package/Config.in                                          |  4 ++++
>  package/perl-xml-libxml/Config.in                          | 10 ++++++++++
>  package/perl-xml-libxml/perl-xml-libxml.mk                 | 14 ++++++++++++++
>  package/perl-xml-namespacesupport/Config.in                |  6 ++++++
>  .../perl-xml-namespacesupport/perl-xml-namespacesupport.mk | 13 +++++++++++++
>  package/perl-xml-sax-base/Config.in                        |  6 ++++++
>  package/perl-xml-sax-base/perl-xml-sax-base.mk             | 13 +++++++++++++
>  package/perl-xml-sax/Config.in                             |  8 ++++++++
>  package/perl-xml-sax/perl-xml-sax.mk                       | 14 ++++++++++++++
>  9 files changed, 88 insertions(+)
>  create mode 100644 package/perl-xml-libxml/Config.in
>  create mode 100644 package/perl-xml-libxml/perl-xml-libxml.mk
>  create mode 100644 package/perl-xml-namespacesupport/Config.in
>  create mode 100644 package/perl-xml-namespacesupport/perl-xml-namespacesupport.mk
>  create mode 100644 package/perl-xml-sax-base/Config.in
>  create mode 100644 package/perl-xml-sax-base/perl-xml-sax-base.mk
>  create mode 100644 package/perl-xml-sax/Config.in
>  create mode 100644 package/perl-xml-sax/perl-xml-sax.mk


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-06-24  5:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 18:14 [Buildroot] [PATCH 1/3] support/script/cpan: improve Makefile generation Francois Perrad
2014-06-23 18:14 ` [Buildroot] [PATCH 2/3] perl-net-ssleay: new package Francois Perrad
2014-06-24  5:22   ` Arnout Vandecappelle
2014-06-29  8:46   ` Thomas Petazzoni
2014-06-23 18:14 ` [Buildroot] [PATCH 3/3] perl-xml-libxml: " Francois Perrad
2014-06-24  5:29   ` Arnout Vandecappelle [this message]
2014-06-29  8:51   ` Thomas Petazzoni
2014-06-29 14:54     ` Thomas Petazzoni
2014-06-24  5:21 ` [Buildroot] [PATCH 1/3] support/script/cpan: improve Makefile generation Arnout Vandecappelle
2014-06-29  8:45 ` 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=53A90CBD.6000904@mind.be \
    --to=arnout@mind.be \
    --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