From: Elijah Newren <newren@gmail.com>
To: Jaydeep Das <jaydeepjd.8914@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: A new feature command request `cmd_ignore`
Date: Fri, 14 Jan 2022 21:17:25 -0800 [thread overview]
Message-ID: <CABPp-BFY2issEqOj1Oj71k=494vc8E563CndxPZfXYrteFoNhw@mail.gmail.com> (raw)
In-Reply-To: <11860e44-beff-39e6-2efc-53324223caee@gmail.com>
On Fri, Jan 14, 2022 at 3:03 PM Jaydeep Das <jaydeepjd.8914@gmail.com> wrote:
>
> Generally, To ignore files from a repository, we just have to add the
> file name in `.gitignore`. But this task becomes a bit
> tedious when there are a lot of unstaged files which you want to ignore.
'unstaged' implies the file is tracked (i.e. previously added), but
has local changes. I think you mean 'untracked' here.
> `git ignore [file names]`
>
> would add that file to `.gitignore`
If there are lots of untracked files, why is it less tedious to type
all of them on the command line, then to type all of them in the
.gitignore file? I don't see what effort is being saved.
> and other parameters like `--force`
> could be added which would delete that file cache if that
> file was already committed.
I don't understand what you mean by this.
next prev parent reply other threads:[~2022-01-15 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 18:58 A new feature command request `cmd_ignore` Jaydeep Das
2022-01-15 5:17 ` Elijah Newren [this message]
2022-01-15 9:03 ` Johannes Sixt
2022-01-15 10:45 ` Jaydeep Das
2022-01-15 15:38 ` Johannes Sixt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BFY2issEqOj1Oj71k=494vc8E563CndxPZfXYrteFoNhw@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaydeepjd.8914@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).