From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/nodejs: bump version to 10.15.3
Date: Fri, 15 Mar 2019 22:20:41 +0100 [thread overview]
Message-ID: <20190315222041.4940f011@windsurf> (raw)
In-Reply-To: <20190314133813.727-2-martin@barkynet.com>
Hello Martin,
On Thu, 14 Mar 2019 13:38:11 +0000
Martin Bark <martin@barkynet.com> wrote:
> See https://nodejs.org/en/blog/release/v10.15.3/
>
> Signed-off-by: Martin Bark <martin@barkynet.com>
This commit log was really too terse, so I have extended it with some
explanation about the torque issue (hopefully I got it right).
Generally speaking, you have put too much information in the cover
letter, and too little in the commit log. The opposite is preferred,
because the commit logs stay forever in the Git history, and are much
more easily associated to a given change in a package, compared to a
cover letter than becomes buried deep down in the mailing list archives.
> + $(INSTALL) -m755 -D $(@D)/out/Release/torque $(HOST_DIR)/usr/bin/torque
I changed to install to $(HOST_DIR)/bin/torque. We no longer have
$(HOST_DIR)/usr, it's a symlink to $(HOST_DIR).
> + # use host version of torque
> + sed "s#<(PRODUCT_DIR)/<(EXECUTABLE_PREFIX)torque<(EXECUTABLE_SUFFIX)#$(HOST_DIR)/usr/bin/torque#" \
And I changed it here as well.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-15 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 13:38 [Buildroot] [PATCH 0/3] Update nodejs to 10.x LTS branch Martin Bark
2019-03-14 13:38 ` [Buildroot] [PATCH 1/3] package/nodejs: bump version to 10.15.3 Martin Bark
2019-03-15 21:20 ` Thomas Petazzoni [this message]
2019-03-14 13:38 ` [Buildroot] [PATCH 2/3] package/nghttp2: bump version to 1.37.0 Martin Bark
2019-03-15 21:20 ` Thomas Petazzoni
2019-03-14 13:38 ` [Buildroot] [PATCH 3/3] package/nodejs: use shared nghttp2 library Martin Bark
2019-03-15 21:20 ` 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=20190315222041.4940f011@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox