From: Chris Marusich <cmmarusich@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 29891@debbugs.gnu.org
Subject: [bug#29891] [PATCH] gnu: java-classpathx-servletapi: Update to 3.0-r1244.
Date: Mon, 08 Jan 2018 23:25:18 -0800 [thread overview]
Message-ID: <87d12jh4td.fsf@gmail.com> (raw)
In-Reply-To: <20180107221142.17118-1-boskovits@gmail.com> ("Gábor Boskovits"'s message of "Sun, 7 Jan 2018 23:11:42 +0100")
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
Gábor Boskovits <boskovits@gmail.com> writes:
> * gnu/packages/java.scm (java-classpathx-servletapi): Update to 3.0-r1244.
This seems correct to me. I also verified that this builds
reproducibly.
The commit message is a bit long; we could summarize it with a sentence
instead.
How difficult would it be to have upstream make a new release? It looks
like we're now using an arbitrary revision of their source code, instead
of a release. In general, I think it's better to use a release if we
can, since that implies the code has been more thoroughly tested etc.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-09 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 13:41 [bug#29891] [PATCH core-updates] gnu: java-classpathx-servletapi: Update to 3.0-r1244 Gábor Boskovits
2018-01-07 22:11 ` [bug#29891] [PATCH] " Gábor Boskovits
2018-01-07 22:13 ` Gábor Boskovits
2018-01-09 7:25 ` Chris Marusich [this message]
2018-01-09 9:59 ` Gábor Boskovits
2018-01-09 10:55 ` Gábor Boskovits
2018-01-09 10:56 ` Gábor Boskovits
2018-01-14 2:25 ` Chris Marusich
2018-01-14 9:07 ` Gábor Boskovits
2018-01-14 15:04 ` Tobias Geerinckx-Rice
2018-01-14 15:28 ` Gábor Boskovits
2018-01-15 8:27 ` [bug#29891] [PATCH] gnu: java-classpathx-servletapi: Update to 3.0.1 Gábor Boskovits
2018-01-16 8:03 ` bug#29891: " Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d12jh4td.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=29891@debbugs.gnu.org \
--cc=boskovits@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).