From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ghostscript: bump version to 9.22
Date: Tue, 17 Oct 2017 15:20:34 +0200 [thread overview]
Message-ID: <20171017152034.186a2858@windsurf.lan> (raw)
In-Reply-To: <20171017121837.18309-1-olivier.schonken@gmail.com>
Hello,
On Tue, 17 Oct 2017 14:18:37 +0200, Olivier Schonken wrote:
> Remove patches that has been merged/updated upstream
When possible, giving the link to the upstream commit is nice. It
allows to quickly double check what the upstream commit looks like
compared to what we had in Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-17 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:18 [Buildroot] [PATCH v2] ghostscript: bump version to 9.22 Olivier Schonken
2017-10-17 12:25 ` Baruch Siach
2017-10-17 13:20 ` Thomas Petazzoni [this message]
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=20171017152034.186a2858@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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