edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Sebastian Humenda <shumenda@gmx.de>
To: edbrowse-dev@edbrowse.org
Subject: Re: QuickJS and maintenance
Date: Sat, 11 Feb 2023 10:56:17 +0100	[thread overview]
Message-ID: <Y+dmQcGc/hKFAA2t@kraftkrust> (raw)
In-Reply-To: <Y+dNkcA27r71/O53@pinebook-pro>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]


[please don't CC me as I'm on the list]
Adam Thompson schrieb am 11.02.2023,  8:10 +0000:
>No problem. As someone who uses Debian on a daily basis I've been wondering
>how to facilitate a more up-to-date Edbrowse package for a while.

Have ou been thinking about stable or about the rolling release versions, i.e.
testing that didn't get updated in time? The a11y team is a bit understaffed.
Depending on how it goes with QuickJS, I could try to follow edbrowse
development along and update the packaging in time. However, for Debian
stable, I cannot make any promise for the time being, as this creates
additional effort -- but let's see. In any case, please feel free to drop in
#debian-a11y or ping me off-list if you need packaging updates.

>That being said, to repeat what I said in my previous email, it's probably
>worth contacting the Quickjs maintainers directly about these concerns as
>they may be able to provide greater reassurance and assistance than we can.

Agreed and on the To-Do-list.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-11  9:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  9:32 Sebastian Humenda
2023-02-08 10:33 ` Karl Dahlke
2023-02-09  8:13   ` Adam Thompson
2023-02-09  9:48     ` Sebastian Humenda
2023-02-11  8:10       ` Adam Thompson
2023-02-11  9:56         ` Sebastian Humenda [this message]
2023-02-11 10:32           ` Karl Dahlke
2023-02-12  7:39             ` Sebastian Humenda
2023-02-12 18:54               ` Adam Thompson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y+dmQcGc/hKFAA2t@kraftkrust \
    --to=shumenda@gmx.de \
    --cc=edbrowse-dev@edbrowse.org \


* 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;
as well as URLs for NNTP newsgroup(s).