From: Frank Pursel <frank.pursel@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 32947@debbugs.gnu.org
Subject: [bug#32947] Add java-xalan.
Date: Tue, 19 Apr 2022 17:13:33 +0000 [thread overview]
Message-ID: <CANp2FMfBCGoL9BJ0gt58hTiQT7Nz9W9gTN3uZ0cFm3K=+wcW6w@mail.gmail.com> (raw)
In-Reply-To: <a8d039feb814ed1f886dd9494de0fd58cbe8463d.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
I concur. WDYT is next?
Thanks,
Frank
(acrow#guix)
On Sat, Apr 16, 2022 at 9:02 PM Maxime Devos <maximedevos@telenet.be> wrote:
> Hi,
>
> While looking superficially into the source for problems isn't a slow
> process (I didn't time it thoroughly but I'd say 20 minutes for 10% or
> so, and possibly less if the files are small, or maybe more if the
> timing was inaccurate or unrepresentative), I'm not exactly swimming in
> free time or something, so don't expect an ‘it's done!’ response
> anytime soon.
>
> I see two options here:
>
> * you could look into the rest yourself (though technically a COI I
> suppose ...)
>
> * consider the current checks into the source code to be sufficient
>
> Also, about the IntStack thing:
>
> * as you wrote, upstream has modified it a lot
> * IIRC and IIUC (though I only looked rather superficially) it's
> a rather basic class anyway, probably not many other plausible
> ways to do it. Also tiny.
> * current OpenJDK's are freely licensed anyway
> * upstream has been asked what, exactly, is the situation
> (though it hasn't been answered yet)
> * so I don't think this is a blocker
>
> Greetings,
> Maxime.
>
[-- Attachment #2: Type: text/html, Size: 1684 bytes --]
next prev parent reply other threads:[~2022-04-19 17:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 15:18 [bug#32947] [PATCH 0/3] Add java-xalan Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 2/3] gnu: Add java-jakarta-regexp Danny Milosavljevic
2018-10-05 15:20 ` [bug#32947] [PATCH 3/3] gnu: Add java-xalan Danny Milosavljevic
2018-10-05 15:46 ` Julien Lepiller
2018-10-05 15:28 ` [bug#32947] [PATCH 1/3] gnu: Add java-cup Julien Lepiller
2018-10-05 16:00 ` Danny Milosavljevic
2018-10-05 16:13 ` Julien Lepiller
2018-10-05 15:52 ` Julien Lepiller
2018-12-19 14:05 ` [bug#32947] Add java-xalan Julien Lepiller
2022-03-17 21:08 ` Frank Pursel
2022-03-17 21:50 ` Maxime Devos
2022-03-17 21:53 ` Maxime Devos
2022-03-17 21:57 ` Maxime Devos
2022-03-18 17:40 ` Maxime Devos
2022-03-18 18:15 ` Frank Pursel
2022-03-18 18:22 ` Frank Pursel
2022-03-18 19:19 ` Maxime Devos
2022-03-18 17:29 ` Frank Pursel
2022-03-18 17:59 ` Maxime Devos
2022-03-18 19:16 ` Frank Pursel
2022-03-18 20:07 ` Maxime Devos
2022-03-18 20:42 ` Frank Pursel
2022-03-19 15:58 ` Maxime Devos
2022-03-22 17:45 ` Maxime Devos
2022-03-22 18:18 ` Julien Lepiller
2022-03-30 17:43 ` Maxime Devos
2022-03-30 18:41 ` Maxime Devos
2022-03-30 20:23 ` Frank Pursel
2022-04-03 8:32 ` Maxime Devos
2022-04-05 13:12 ` Maxime Devos
2022-04-05 21:09 ` Frank Pursel
2022-04-09 13:40 ` Maxime Devos
2022-04-11 16:36 ` Frank Pursel
2022-04-12 9:32 ` Maxime Devos
2022-04-13 23:43 ` Frank Pursel
2022-04-14 8:30 ` Maxime Devos
2022-04-14 16:07 ` Frank Pursel
2022-04-14 20:33 ` Maxime Devos
2022-04-14 20:49 ` Frank Pursel
2022-04-16 21:02 ` Maxime Devos
2022-04-19 17:13 ` Frank Pursel [this message]
2022-04-19 18:44 ` Maxime Devos
2022-04-19 18:55 ` Frank Pursel
2022-03-19 15:41 ` Frank Pursel
2022-03-19 16:38 ` Frank Pursel
2022-03-23 1:32 ` Frank Pursel
2022-03-23 14:14 ` Frank Pursel
2022-08-19 22:05 ` Vagrant Cascadian
2022-06-24 15:23 ` [bug#32947] [PATCH 0/3] Add java-xalan: reverse ping Maxime Devos
2022-07-14 23:46 ` [bug#32947] [PATCH 0/3] Add java-xalan Frank Pursel
2022-08-20 0:57 ` [bug#32947] Add java-xalan-interp Frank Pursel
2022-09-20 21:25 ` [bug#32947] Add java-xalan-interp CVE Frank Pursel
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='CANp2FMfBCGoL9BJ0gt58hTiQT7Nz9W9gTN3uZ0cFm3K=+wcW6w@mail.gmail.com' \
--to=frank.pursel@gmail.com \
--cc=32947@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.