All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 63471] New: Please add a "quit" command to the e2fsck interactive mode
Date: Tue, 22 Oct 2013 07:16:05 +0000	[thread overview]
Message-ID: <bug-63471-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=63471

            Bug ID: 63471
           Summary: Please add a "quit" command to the e2fsck interactive
                    mode
           Product: File System
           Version: 2.5
    Kernel Version: 3.11.6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: unforgettableid@gmail.com
                CC: tytso@mit.edu
        Regression: No

Some users don't know whether or not it is safe to exit e2fsck using Ctrl+C.

It would be great if you could please add a "quit" command to the e2fsck
interactive mode. The "quit" command should quit e2fsck, leaving users
confident that they didn't cause any extra damage to the filesystem by quitting
early.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-10-22  7:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  7:16 bugzilla-daemon [this message]
2013-10-23  2:07 ` [Bug 63471] Please add a "quit" command to the e2fsck interactive mode bugzilla-daemon
2013-10-31  1:11 ` bugzilla-daemon
2013-11-13 12:08 ` bugzilla-daemon
2013-11-13 12:08 ` bugzilla-daemon
2021-02-09 20:56 ` bugzilla-daemon

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=bug-63471-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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.