All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: "David Sterba" <dsterba@suse.cz>,
	"Holger Hoffstätte" <holger@applied-asynchrony.com>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Scrub resume regression
Date: Fri, 17 Jan 2020 11:39:27 -0700	[thread overview]
Message-ID: <CAJCQCtTZMSzNosnognWCyBU+iJ4La=0EG0xBKHEPSDdaAAqt4A@mail.gmail.com> (raw)
In-Reply-To: <20200117155948.GM13306@hungrycats.org>

It's no one's fault, it's just confusing. :P

Cancel word origin means more than stop, implies resetting state, to
obliterate or invalidate.

Pause and stop word origin suggests they're interchangeable, but in
practice with digital audio and video consumer gear, stop has come to
mean a kind of cancel. (I'm gonna ignore tape.) Where a start from a
stop will start at the very beginning. Whereas pause saves state and
unpause means resume.

Lightweight change, add new command stop, which saves state, and
cancel is an alias for backward compatibility. No other change.

Moderate change:
start = alias resume
stop = alias cancel
i.e. a stop then start does the same thing as a cancel then resume,
unless new command 'reset' is used
reset = stops, and resets state to the beginning

Heavier change that's linguistically sane, but breaks expectations of
today's cancel:
pause and unpause (alias resume), and start and stop (alias cancel).
The former is stateful, and the latter is stateless.

But this problem should be looked at by i18n folks before changing anything.

---
Chris Murphy

  reply	other threads:[~2020-01-17 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  9:03 Scrub resume regression Graham Cobb
2020-01-15  9:33 ` Filipe Manana
2020-01-15 11:55   ` Graham Cobb
2020-01-15 12:51 ` David Sterba
2020-01-15 13:10   ` Holger Hoffstätte
2020-01-15 21:02     ` Sebastian Döring
2020-01-16 14:02     ` David Sterba
2020-01-17 15:59       ` Zygo Blaxell
2020-01-17 18:39         ` Chris Murphy [this message]
2020-01-17 19:39           ` Graham Cobb

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='CAJCQCtTZMSzNosnognWCyBU+iJ4La=0EG0xBKHEPSDdaAAqt4A@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=dsterba@suse.cz \
    --cc=holger@applied-asynchrony.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.