all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: bokr@bokr.com
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
	Morgan.J.Smith@outlook.com, 56382@debbugs.gnu.org,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	20255@debbugs.gnu.org
Subject: bug#20255: [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup
Date: Tue, 19 Jul 2022 10:29:59 +0200	[thread overview]
Message-ID: <871quhwlmg.fsf@gnu.org> (raw)
In-Reply-To: <20220718133318.GA2771@LionPure> (bokr@bokr.com's message of "Mon, 18 Jul 2022 15:33:18 +0200")

Hi,

bokr@bokr.com skribis:

> I'm sure you were just after a quick indication and know what can affect timing,
> but I'm curious:
>
> What would the above results be if you did the second timing
> first, after a power down and cold start?
>
> I'm guessing the kernel file systems are pretty clever about
> caching stuff, especially if you have lots of ram :)

The ‘drop_caches’ command is meant to drop all caches, as if I were
doing it on a cold start.

Ludo’.




  reply	other threads:[~2022-07-19  8:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 13:43 [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup Morgan.J.Smith
2022-07-12 22:15 ` Ludovic Courtès
2022-07-13  8:54 ` Raghav Gururajan via Guix-patches via
2022-07-13 16:06   ` Raghav Gururajan via Guix-patches via
2022-07-15 13:02   ` Ludovic Courtès
2022-07-16  1:38     ` Maxim Cournoyer
2022-07-18  9:29       ` Ludovic Courtès
2022-07-18 11:21         ` bug#20255: " Maxim Cournoyer
2022-07-18 13:33         ` [bug#56382] " bokr
2022-07-19  8:29           ` Ludovic Courtès [this message]
2022-07-18 15:19       ` Raghav Gururajan via Guix-patches via

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=871quhwlmg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=20255@debbugs.gnu.org \
    --cc=56382@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.com \
    --cc=bokr@bokr.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.