All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Hugo Mills <hugo@carfax.org.uk>,
	Filipe Manana <fdmanana@kernel.org>,
	Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	Josef Bacik <josef@toxicpanda.com>
Subject: Re: [bug] GNOME loses all settings following failure to resume from suspend
Date: Thu, 6 Jan 2022 22:07:10 +0100	[thread overview]
Message-ID: <YddZ/vTFK510d8zp@angband.pl> (raw)
In-Reply-To: <20220106102056.GH14058@savella.carfax.org.uk>

On Thu, Jan 06, 2022 at 10:20:56AM +0000, Hugo Mills wrote:
>    Since I can't find an "fsync" command line tool

sync /the/file


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Certified airhead; got the CT scan to prove that!
⠈⠳⣄⠀⠀⠀⠀

  parent reply	other threads:[~2022-01-06 21:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 17:34 [bug] GNOME loses all settings following failure to resume from suspend Chris Murphy
2022-01-05 18:04 ` Filipe Manana
2022-01-05 18:32   ` Filipe Manana
2022-01-05 18:34   ` Hugo Mills
2022-01-05 20:38     ` Filipe Manana
2022-01-05 21:31       ` Hugo Mills
2022-01-05 21:39         ` Hugo Mills
2022-01-05 21:53           ` Hugo Mills
2022-01-06  9:51             ` Filipe Manana
2022-01-06 10:20               ` Hugo Mills
2022-01-06 10:27                 ` Filipe Manana
2022-01-06 20:02                   ` Chris Murphy
2022-01-06 20:06                     ` Chris Murphy
2022-01-06 20:23                       ` Hugo Mills
2022-01-06 21:07                 ` Adam Borowski [this message]
2022-01-05 18:40   ` Chris Murphy
2022-01-05 20:32     ` Filipe Manana
2022-01-09 17:04   ` Remi Gauvin

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=YddZ/vTFK510d8zp@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=fdmanana@kernel.org \
    --cc=hugo@carfax.org.uk \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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. 
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.