From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Leo Prikler <leo.prikler@student.tugraz.at>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
35594@debbugs.gnu.org, 36376@debbugs.gnu.org
Subject: bug#35594: bug#36376: Application menu of desktop environment not automatically updated
Date: Tue, 10 Nov 2020 18:48:53 +0100 [thread overview]
Message-ID: <CAJ3okZ216jq9Q=ML-yFN-CW-P95sHV5KDAQcw_7O7YJ6Uc-Gvg@mail.gmail.com> (raw)
In-Reply-To: <87lff9nsl0.fsf@gnu.org>
On Tue, 10 Nov 2020 at 16:25, Ludovic Courtès <ludo@gnu.org> wrote:
> Video!
Héhé! Nice :-)
> So I think we should include this fix in 1.2. What do people think?
You mean only the initial patch. If it works in "real conditions" for
bob on 'antelope' (desktop.tmpl), then it would nice to have for 1.2,
> The main downside is extra grafting, which means extra disk and CPU
> usage for our users. However, libx11 (11K dependents) is also grafted,
> so it shouldn’t make things worse (GLib has 6K dependents).
No free lunch. :-)
Is it really slow or acceptable?
All the best,
simon
next prev parent reply other threads:[~2020-11-10 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:12 bug#36376: Application menu of desktop environment not automatically updated Ludovic Courtès
2020-11-03 22:46 ` Ludovic Courtès
2020-11-03 23:28 ` Leo Prikler
2020-11-04 21:41 ` bug#35594: " Maxim Cournoyer
2020-11-04 22:15 ` Ludovic Courtès
2020-11-05 6:38 ` Maxim Cournoyer
2020-11-06 16:02 ` Ludovic Courtès
2020-11-06 18:56 ` Maxim Cournoyer
2020-11-10 15:23 ` Ludovic Courtès
2020-11-10 17:48 ` zimoun [this message]
2020-11-10 21:23 ` Ludovic Courtès
2020-11-12 15:56 ` bug#35594: " Ludovic Courtès
2020-11-13 20:38 ` bug#36376: " Ludovic Courtès
2020-11-17 4:57 ` Maxim Cournoyer
2020-11-17 9:08 ` Ludovic Courtès
2020-11-18 4:34 ` Maxim Cournoyer
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='CAJ3okZ216jq9Q=ML-yFN-CW-P95sHV5KDAQcw_7O7YJ6Uc-Gvg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=35594@debbugs.gnu.org \
--cc=36376@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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).