From: ajtcode71 <ajtcode71@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: darktable: update to 4.0.0
Date: Wed, 10 Aug 2022 10:01:07 +0200 [thread overview]
Message-ID: <20220810080107.xOpEFk-0D_0Br_fwRcOXNzAGP-H-X6E8zwIoSXWnzbk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38336@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
New comment by ajtcode71 on void-packages repository
https://github.com/void-linux/void-packages/pull/38336#issuecomment-1210306557
Comment:
> So, I haven't updated the package to `4.0.0` because things tend to break on major versions with darktable. I have `4.0.0` running locally, but there are hand full of small issues I didn't want everyone else to experience. I'd rather wait for a `4.0.1`.
>
> Sorry I didn't see this earlier. Please @ me next time.
Ok no problem.. Should I close this PR?
next prev parent reply other threads:[~2022-08-10 8:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 15:22 [PR PATCH] New Version 4.0.0 - Test compiled amd64 and aarch64 ajtcode71
2022-07-28 15:30 ` [PR PATCH] [Updated] " ajtcode71
2022-07-28 15:37 ` darktable: update to 4.0.0 CameronNemo
2022-07-28 15:44 ` tranzystorek-io
2022-07-28 16:25 ` [PR PATCH] [Updated] " ajtcode71
2022-07-28 16:40 ` ajtcode71
2022-07-31 6:49 ` ajtcode71
2022-07-31 7:07 ` [PR PATCH] [Updated] " ajtcode71
2022-07-31 7:12 ` CameronNemo
2022-08-01 4:00 ` ajtcode71
2022-08-05 23:49 ` abenson
2022-08-07 7:47 ` [PR PATCH] [Updated] " ajtcode71
2022-08-08 7:07 ` ajtcode71
2022-08-09 22:57 ` ajtcode71
2022-08-09 23:11 ` ajtcode71
2022-08-09 23:31 ` ajtcode71
2022-08-09 23:48 ` lemmi
2022-08-10 7:27 ` [PR PATCH] [Updated] " ajtcode71
2022-08-10 7:33 ` ajtcode71
2022-08-10 7:59 ` ajtcode71
2022-08-10 8:01 ` ajtcode71 [this message]
2022-08-10 8:01 ` ajtcode71
2022-08-10 8:43 ` paper42
2022-08-11 0:49 ` lemmi
2022-08-11 0:49 ` [PR PATCH] [Closed]: " lemmi
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=20220810080107.xOpEFk-0D_0Br_fwRcOXNzAGP-H-X6E8zwIoSXWnzbk@z \
--to=ajtcode71@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).