All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: Renato Caldas <rm.santos.caldas@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] perl-ptest.inc: fix tar call to prevent objcopy failure
Date: Fri, 3 Jun 2016 08:50:55 +0200	[thread overview]
Message-ID: <575128CF.8010308@pengutronix.de> (raw)
In-Reply-To: <CA+21M5DUAvp1csE=kARmE2Fg3SyfzxDO0L2GuBsvpSMjiiN2Xg@mail.gmail.com>

Hi Renato,

thanks for the comments on my changes.

On 05/31/2016 01:35 PM, Renato Caldas wrote:
> My suggestion is that you submit a new patch with those improvements
> on top of the quick fix I made. I suggest you also add quotes to the
> --exclude options per tar's man page.

I did not find any hints about quotes, where is it written? It also 
seems to me that the man page in current tar (1.29) is a bit incomplete 
as it does not mention any 'exclude' option, anymore. At least on my 
distro (debian).

> You might also want to simplify the commit message a bit. I'm fairly
> new to yocto (and my view may be wrong), but this is how I would do
> it:
> - change the component name from "perl-ptest.inc:" to "perl:"

Maybe "perl-ptest" would be ok, too, as it matches the resulting 
packages name.

> - use the commit title to describe the change you made, not exactly
> what bug it fixed. Example: "fix tar call according to its man page"
> (or something like that)
> - describe the change in simpler terms. Taking what you wrote, I would
> rewrite it like this:
>
> "The existing tar call on do_install_ptest() did not match the man
> page, but worked with older tar versions. The new 1.29 version of tar
> has stricter argument handling, and future versions may be even
> stricter. Failure to use it according to its manual may result in
> arguments being silently ignored and breaking the build."
>

Yes, sounds good to me. And my original message does not match the 
remaining changes anymore. Is it ok if I take your text, and add you as 
Signed-off for the patch then?

>
> So while changing the position of the "*" fixed it for tar 1.29, your
> proposed changes are important to future-proof the perl recipe for
> newer tar versions. As such, please do submit a new patch.

I will do so, then.


Best regard, Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2016-06-03  6:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 11:53 [PATCH] perl: reorder tar arguments in do_install_ptest() Renato Caldas
2016-05-30 13:04 ` [PATCH] perl-ptest.inc: fix tar call to prevent objcopy failure Enrico Jorns
2016-05-31 11:35   ` Renato Caldas
2016-06-03  6:50     ` Enrico Joerns [this message]
2016-06-06 11:35       ` Renato Caldas
2016-05-30 20:11 ` [PATCH] perl: reorder tar arguments in do_install_ptest() Aníbal Limón
2016-05-30 20:39   ` Renato Caldas
2016-05-30 21:06     ` Aníbal Limón
2016-05-30 21:17       ` Aníbal Limón
2016-05-30 21:35         ` Renato Caldas
2016-06-29  8:54 ` [PATCH][jethro] perl-ptest.inc: fix tar call to prevent objcopy failure Enrico Jorns
2016-06-29  8:54 ` [PATCH][krogoth] " Enrico Jorns

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=575128CF.8010308@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rm.santos.caldas@gmail.com \
    /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.