From: Leo Famulari <leo@famulari.name>
To: 31322@debbugs.gnu.org
Subject: [bug#31322] GIMP 2.10.0 update
Date: Mon, 30 Apr 2018 16:45:34 -0400 [thread overview]
Message-ID: <20180430204534.GA1886@jasmine.lan> (raw)
In-Reply-To: <20180430203737.GA398@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
On Mon, Apr 30, 2018 at 04:37:37PM -0400, Leo Famulari wrote:
> The following patch series updates GIMP to the new release, 2.10.0.
>
> I tested on x86_64-linux (foreign distro) by doing some very basic
> operations, like opening and editing some images, and exporting the
> results.
By the way, I found some minor issues in these patches with `guix lint`.
All these issues will be fixed before pushing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-30 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 20:37 [bug#31322] GIMP 2.10.0 update Leo Famulari
2018-04-30 20:38 ` [bug#31322] [PATCH 1/6] gnu: Add libmypaint Leo Famulari
2018-04-30 20:38 ` [bug#31322] [PATCH 2/6] gnu: Add mypaint-brushes Leo Famulari
2018-04-30 22:20 ` Marius Bakke
2018-04-30 20:38 ` [bug#31322] [PATCH 3/6] gnu: Add poppler-data Leo Famulari
2018-04-30 22:40 ` Marius Bakke
2018-05-01 0:55 ` Leo Famulari
2018-04-30 20:38 ` [bug#31322] [PATCH 4/6] gnu: gegl: Update to 0.4 Leo Famulari
2018-04-30 20:38 ` [bug#31322] [PATCH 5/6] gnu: babl: Update to 0.1.46 Leo Famulari
2018-04-30 20:38 ` [bug#31322] [PATCH 6/6] gnu: gimp: Update to 2.10.0 Leo Famulari
2018-04-30 22:19 ` [bug#31322] [PATCH 1/6] gnu: Add libmypaint Marius Bakke
2018-04-30 20:45 ` Leo Famulari [this message]
2018-04-30 22:44 ` [bug#31322] GIMP 2.10.0 update Marius Bakke
2018-05-01 1:49 ` bug#31322: " Leo Famulari
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=20180430204534.GA1886@jasmine.lan \
--to=leo@famulari.name \
--cc=31322@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.