From: Junio C Hamano <gitster@pobox.com>
To: Cameron Boehmer <cameron.boehmer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git clean --local
Date: Sun, 02 Dec 2018 13:43:59 +0900 [thread overview]
Message-ID: <xmqqo9a4ilm8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqsgzgiyk2.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Sun, 02 Dec 2018 09:04:29 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> Cameron Boehmer <cameron.boehmer@gmail.com> writes:
>
>> 1) add a new flag
>> -l, --local
>> Do not consult git config --global core.excludesFile in
>> determining what files git ignores. This is useful in conjunction with
>> -x/-X to preserve user files while removing build artifacts.
> ...
> But it might be useful as an option that affects any "git" command,
> e.g. "git --local-config-only clean". I dunno.
If you only want to say "there is no global excludes file", perhaps
$ git -c core.excludesFile=/dev/null clean -x
may be sufficient, so for that particular use case, there is no need
to introduce a new command, I'd think.
In the longer term, however, I think we would want to introduce a
distinction among ignored files---we only support "ignored and
expendable" class, but not "ignored but precious" class. With the
latter class introduced, it would make sense for "git clean -x/-X"
to notice that a path is ignored but precious and keep it. If a
dir/foo is ignored, dir/bar is tracked in commit A that is currently
checked out, and there is no dir/ directory in commit B, checking
out commit B would remove dir/foo (because the last tracked file in
the directory goes away and all remaining files in the directory
would be ignored but expendable). But if we introduced a new
"ignored but precious" class and made dir/foo a member of such a
class, then you will be prevented from checkout out B until you do
something about dir/foo that is now "precious".
next prev parent reply other threads:[~2018-12-02 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 22:51 [RFC] git clean --local Cameron Boehmer
2018-12-02 0:04 ` Junio C Hamano
2018-12-02 4:43 ` Junio C Hamano [this message]
2018-12-02 13:25 ` Ævar Arnfjörð Bjarmason
2018-12-02 17:37 ` Randall S. Becker
2018-12-02 19:37 ` Junio C Hamano
2018-12-03 7:40 ` Cameron Boehmer
2018-12-04 2:45 ` 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
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=xmqqo9a4ilm8.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=cameron.boehmer@gmail.com \
--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.
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).