From: Ricardo Wurmus <rekado@elephly.net>
To: mike.rosset@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: qtwenengine anybody?
Date: Wed, 18 Dec 2019 23:46:55 +0100 [thread overview]
Message-ID: <87o8w5qmjk.fsf@elephly.net> (raw)
In-Reply-To: <87d0clpbt6.fsf@gmail.com>
mike.rosset@gmail.com writes:
> Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
>
>> Am 16.12.19 um 18:09 schrieb mike.rosset@gmail.com:
>>> I'm currently brushing up my latest qtwebengine build. Will resubmit
>>> this patch. I will also see if I can inherit qtsvg again to put this
>>> back on par with other module packages. From there I'll put a simple
>>> test example together demonstrating the locale and translation problem.
>>
>> Sounds good
>
> I've resubmitted the patch it can be found here
> https://lists.gnu.org/archive/html/guix-patches/2019-12/msg00530.html. My
> ML patch workflow is probably not all that correct so I apologize if
> there is any issues.
For those following along at home: here it is in the bug tracker:
https://issues.guix.gnu.org/issue/35866
--
Ricardo
next prev parent reply other threads:[~2019-12-18 22:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 12:55 qtwenengine anybody? Hartmut Goebel
2019-12-16 13:42 ` Pierre Neidhardt
2019-12-16 14:13 ` mike.rosset
2019-12-16 14:15 ` Pierre Neidhardt
2019-12-16 15:19 ` mike.rosset
2019-12-16 15:22 ` Hartmut Goebel
2019-12-16 15:45 ` mike.rosset
2019-12-16 15:57 ` Hartmut Goebel
2019-12-16 17:09 ` mike.rosset
2019-12-16 17:29 ` Hartmut Goebel
2019-12-18 21:24 ` mike.rosset
2019-12-18 22:03 ` Pierre Neidhardt
2019-12-18 22:30 ` mike.rosset
2019-12-19 18:23 ` Pierre Neidhardt
2019-12-19 19:47 ` mike.rosset
2019-12-19 20:36 ` Pierre Neidhardt
2019-12-20 0:16 ` mike.rosset
2019-12-20 10:46 ` Pierre Neidhardt
2019-12-20 10:53 ` Pierre Neidhardt
2019-12-18 22:46 ` Ricardo Wurmus [this message]
2019-12-20 10:49 ` Pierre Neidhardt
2019-12-20 16:04 ` mike.rosset
2019-12-20 16:16 ` Pierre Neidhardt
2019-12-20 16:44 ` mike.rosset
2019-12-31 13:48 ` Pierre Neidhardt
2019-12-31 13:50 ` Pierre Neidhardt
2020-01-01 17:34 ` mike.rosset
2020-01-01 20:43 ` Pierre Neidhardt
2020-01-01 22:30 ` mike.rosset
2020-01-02 12:29 ` Hartmut Goebel
2020-01-02 20:24 ` mike.rosset
2020-01-03 14:57 ` Hartmut Goebel
2020-01-05 16:10 ` mike.rosset
2020-01-05 16:47 ` Hartmut Goebel
2020-01-01 22:46 ` Ricardo Wurmus
2020-01-02 10:52 ` Pierre Neidhardt
2020-01-05 14:59 ` mike.rosset
2020-01-05 19:52 ` Ricardo Wurmus
2020-01-06 5:11 ` mike.rosset
2020-01-06 19:23 ` Marius Bakke
2020-01-07 0:27 ` mike.rosset
2020-01-07 10:26 ` Hartmut Goebel
2020-01-07 19:28 ` mike.rosset
2020-01-11 17:39 ` Marius Bakke
2020-01-11 17:40 ` Pierre Neidhardt
2020-01-11 18:19 ` Mike Rosset
2020-01-11 18:28 ` Pierre Neidhardt
2020-01-13 10:54 ` Mike Rosset
2020-01-13 14:26 ` Pierre Neidhardt
2020-01-13 18:37 ` Mike Rosset
2020-01-11 18:14 ` Mike Rosset
2020-01-07 8:09 ` Pierre Neidhardt
2020-01-07 19:14 ` mike.rosset
2020-01-07 8:12 ` Pierre Neidhardt
2020-01-07 22:49 ` Marius Bakke
2020-01-01 17:22 ` mike.rosset
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=87o8w5qmjk.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mike.rosset@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).