From: John Kehayias <john.kehayias@protonmail.com>
To: Alex Devaure <ajadevaure@gmail.com>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel@gnu.org, Vinicius Monego <monego@posteo.net>,
67719-done@debbugs.gnu.org, 68293-done@debbugs.gnu.org
Subject: Re: update darktable version
Date: Thu, 25 Jan 2024 05:55:37 +0000 [thread overview]
Message-ID: <87jznyhs8f.fsf@protonmail.com> (raw)
In-Reply-To: <87zfwumw9g.fsf@gmail.com>
Hi Alex,
On Wed, Jan 24, 2024 at 06:15 PM, Alex Devaure wrote:
> Hi Maxim,
>
> Thank you for your answer. I created the issue #68293 and the
> modification is now on master branch.
> Best regards,
> Alex
>
Looks like Vinicius Monego already did the update in
9c67673d7bb9cdc43c1196b075447b57aff74039 after pushing #67719 starting
with 50731875243428cb11cc17fa712fa8079b307622.
However, both issues were left open, so I'm closing both with this message.
Sorry for any duplicated work and thanks both of you for keeping
Darktable up to date and improving it!
John
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi Alex,
>>
>> Alex Devaure <ajadevaure@gmail.com> writes:
>>
>>> Hi all,
>>> There is a new version of the RAW developer darktable. The patch #67719
>>> modifies the generation of it by replacing clang with gcc. The patch is
>>> not yet merged, should I base my patch (updating darktable version) to
>>> #67719?
>>
>> That'd be fine, yes.
prev parent reply other threads:[~2024-01-25 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87plyvima5.fsf@gmail.com>
2023-12-24 16:48 ` update darktable version Alex Devaure
2024-01-23 15:26 ` Maxim Cournoyer
2024-01-24 18:15 ` Alex Devaure
2024-01-25 5:55 ` John Kehayias [this message]
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=87jznyhs8f.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=67719-done@debbugs.gnu.org \
--cc=68293-done@debbugs.gnu.org \
--cc=ajadevaure@gmail.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=monego@posteo.net \
/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).