From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 59019C33C9E for ; Fri, 17 Jan 2020 18:39:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2E5BF2072B for ; Fri, 17 Jan 2020 18:39:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=colorremedies-com.20150623.gappssmtp.com header.i=@colorremedies-com.20150623.gappssmtp.com header.b="tZJKt+C7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729354AbgAQSjq (ORCPT ); Fri, 17 Jan 2020 13:39:46 -0500 Received: from mail-wr1-f54.google.com ([209.85.221.54]:34036 "EHLO mail-wr1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726603AbgAQSjq (ORCPT ); Fri, 17 Jan 2020 13:39:46 -0500 Received: by mail-wr1-f54.google.com with SMTP id t2so23708379wrr.1 for ; Fri, 17 Jan 2020 10:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colorremedies-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KlBNYqJDpMz7PSfs7VLAkzpHcNduAsao14hlJo0St0E=; b=tZJKt+C7khZkSfagkclrPoToinyZQzeAbLv95uQ+cZjJ5VD8ZItDSFHjaDL+SMIfiD mPo3rTuF5zD914LuW5CMdNd0B1k7ZiZk9C3HLLo3NgAlGZBsXDZb9nD+WLAjCV9RRrlJ /SZLzXtS4xBqqKXwlRB6YslNzKbIUq/0J/QM7dR+gWFuX6VM6eQsvLLDJ3JGqxF8JgZS MvtDuZK6z4GDvnZV6LoTB/HgKYUOR6Psq28+440rN9FMWNn39QZ4yXKgJr7Q2WApyLJT gWSSJKVrEmVRkKrTtHusYfTwHJ360BBNVvbgs832bQWskzWcYIFtqhLQt/7cY2gMNoDX 5Hkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KlBNYqJDpMz7PSfs7VLAkzpHcNduAsao14hlJo0St0E=; b=o/4EO7BXjnt22dgkDluuRVob6HZ9vZo8TbRwVvViZQ/RccT30jH31aZp/7Y/lW0sif w/T39eoCO2LKRG7VOZ2BkOI7I3MVe41hplBeNoUkQKVpzUAXDBMSOEJBGNooh3P+xHRr yPWxV/D970/fblrCbmYIeKu1uccX6LglQJsUxajT2m2v2XW7YNcmV5UNG+BgIL7Rofpr hpJubhdOALUewvfb+bOHxjdXlATHnGieV+4/9rqH7K+WNvW/zyaL3K4I7JFmzbvUjTim 3DSVwdtCzTZFpKjlNe3n+Rd6xY+DEW9WxrvPfEVnkCpGLidiKdc9NivLlFid+MU5KKwt tAVg== X-Gm-Message-State: APjAAAVtCwH9VeVRqfDFk83HdbCZ8NSGwsUOTErpWH3XUJNjMWrFWahg ed4sKQqHZCdCU1GxPEbetff9qBbjXmbZGfRBMEZRI45p148= X-Google-Smtp-Source: APXvYqy0cioAd8kHhydLG3WM+VwSRF8JraoG5+79zP4DBgQ+sYSZPHiPeOVnAFe/Fn+rYolsfKBlklojAanXkMM83pY= X-Received: by 2002:adf:fa43:: with SMTP id y3mr4540228wrr.65.1579286383744; Fri, 17 Jan 2020 10:39:43 -0800 (PST) MIME-Version: 1.0 References: <20200115125134.GN3929@twin.jikos.cz> <5aa23833-d1e2-fe6f-7c6e-f366d3eccbe3@applied-asynchrony.com> <20200116140227.GV3929@twin.jikos.cz> <20200117155948.GM13306@hungrycats.org> In-Reply-To: <20200117155948.GM13306@hungrycats.org> From: Chris Murphy Date: Fri, 17 Jan 2020 11:39:27 -0700 Message-ID: Subject: Re: Scrub resume regression To: Zygo Blaxell Cc: David Sterba , =?UTF-8?Q?Holger_Hoffst=C3=A4tte?= , Btrfs BTRFS Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.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