From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] at: change upstream site, bump version
Date: Tue, 18 Sep 2018 09:57:26 +0200 [thread overview]
Message-ID: <20180918095726.50623f29@windsurf> (raw)
In-Reply-To: <20180917211219.17868-2-giulio.benetti@micronovasrl.com>
Hello,
Thanks for working on this! This was definitely something that needed
to be done for a long time!
On Mon, 17 Sep 2018 23:12:18 +0200, Giulio Benetti wrote:
> Minicom is now available on a git repository at:
Minicom ? :-)
> https://salsa.debian.org/debian/at
> Main changes 3.1.16 -> 3.1.23:
> - add support for SELinux, multiple files
> - improve atd.service, see bug report 892819
> - fix various bugs and warnings
> - finalized script to release software
>
> So:
> - change AT_SITE_METHOD to git pointing to release/3.1.23
> - update tarball sha256 in hash file
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
> ---
> ...-Makefile-fix-parallel-build-failure.patch | 33 +++++++++++++++++++
Is it really necessary to have a patch that fixes parallel build, if
parallel build is not entirely fixed and you need $(MAKE1) anyway ?
I believe the patch is not necessary. Let's keep MAKE1 for now, and
maybe report the parallel build issue upstream.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-18 7:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 21:12 [Buildroot] [PATCH 0/2] at: bump version Giulio Benetti
2018-09-17 21:12 ` [Buildroot] [PATCH 1/2] at: change upstream site, " Giulio Benetti
2018-09-18 7:57 ` Thomas Petazzoni [this message]
2018-09-18 8:01 ` Giulio Benetti
2018-09-18 9:16 ` Thomas Petazzoni
2018-09-18 20:28 ` Giulio Benetti
2018-09-18 21:39 ` [Buildroot] [PATCH v2 0/2] at: " Giulio Benetti
2018-09-18 21:39 ` [Buildroot] [PATCH v2 1/2] at: change upstream site, " Giulio Benetti
2018-09-18 21:43 ` Giulio Benetti
2018-09-20 4:38 ` Baruch Siach
2018-09-20 16:43 ` Giulio Benetti
2018-09-20 12:43 ` Matthew Weber
2018-09-20 16:47 ` Giulio Benetti
2018-09-18 21:39 ` [Buildroot] [PATCH v2 2/2] at: add sha256 for legal-info files Giulio Benetti
2018-09-19 9:57 ` [Buildroot] [PATCH v2 0/2] at: bump version Giulio Benetti
2018-09-20 16:59 ` [Buildroot] [PATCH v3 " Giulio Benetti
2018-09-20 16:59 ` [Buildroot] [PATCH v3 1/2] at: change upstream site, " Giulio Benetti
2018-09-20 17:40 ` Matthew Weber
2018-09-20 17:42 ` Giulio Benetti
2018-09-20 16:59 ` [Buildroot] [PATCH v3 2/2] at: add sha256 for legal-info files Giulio Benetti
2018-09-23 21:33 ` [Buildroot] [PATCH v3 0/2] at: bump version Thomas Petazzoni
2018-09-23 22:58 ` Giulio Benetti
2018-09-17 21:12 ` [Buildroot] [PATCH 2/2] at: add sha256 for legal-info files Giulio Benetti
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=20180918095726.50623f29@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.