From: Pratyush Yadav <me@yadavpratyush.com>
To: Filipp Bakanov <filipp@bakanov.su>
Cc: git@vger.kernel.org
Subject: Re: Proposal: "unadd" command / alias.
Date: Wed, 28 Oct 2020 18:37:17 +0530 [thread overview]
Message-ID: <87eelifqii.fsf@yadavpratyush.com> (raw)
In-Reply-To: <CAAdniQ5pRHKUU77XVmZkZ_gUgfYYFpo9=Xt2T6EgzJ3hoT0YMg@mail.gmail.com> (Filipp Bakanov's message of "Tue, 27 Oct 2020 23:10:00 +0300")
On Tue, Oct 27 2020, Filipp Bakanov wrote:
> Hi! I suggest to add "unadd" command, that will undo a git add command.
>
> git unadd path/to/file
>
> It will be an alias to:
>
> git reset HEAD -- path/to/file
>
> The motivation is that I always forget syntax and have to google each
> time I want to undo accidentally added files. Unadd is just much
> easier to remember and quite obvious.
Why do you need to Google when `git status` tells you how to do it?
$ touch foo
$ git add foo
$ git status
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: foo
$ git restore --staged foo
$ git status
On branch master
Your branch is up to date with 'origin/master'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
foo
nothing added to commit but untracked files present (use "git add" to track)
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2020-10-28 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 20:10 Proposal: "unadd" command / alias Filipp Bakanov
2020-10-27 20:32 ` Junio C Hamano
2020-10-27 21:56 ` Theodore Y. Ts'o
2020-10-27 22:02 ` Filipp Bakanov
2020-10-27 22:54 ` Theodore Y. Ts'o
2020-10-27 23:14 ` Filipp Bakanov
2020-10-28 11:00 ` Philip Oakley
2020-10-28 12:13 ` Konstantin Tokarev
2020-10-28 12:21 ` Filipp Bakanov
2020-10-28 13:07 ` Pratyush Yadav [this message]
2020-10-28 13:56 ` Filipp Bakanov
2020-10-28 23:44 ` Junio C Hamano
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=87eelifqii.fsf@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=filipp@bakanov.su \
--cc=git@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.