Re: [RFC] git clean --local
- Date: Tue, 04 Dec 2018 11:45:51 +0900
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Subject: Re: [RFC] git clean --local
Junio C Hamano <gitster@xxxxxxxxx> writes:
> If "git clean" takes a pathspec, perhaps you can give a negative
> pathspec to exclude whatever you do not want to get cleaned,
> something like
> git clean '*.o' ':!precious.o'
> to say "presious.o is ignored (hence normally expendable), but I do
> not want to clean it with this invocation of 'git clean'"?
Hmph, this leads me to an interesting thought. With today's code,
these two commands behave in meaningfully different ways when I mark
some paths that match .gitignore patterns with the precious
echo "*.ignored" >>.git/info/exclude
echo "precious.* precious" >>.git/info/attributes
: >expendable.ignored 2>precious.ignored
git clean -n -x
git clean -n -x ':(exclude,attr:precious)'
I am not suggesting that giving "git clean" a configuration knob
that always append pathspec elements, which would allow users to use
the mechanism to set the above magic pathspec, would be a good
approach. If we were to follow through this line of thought, an
obvious thing to do is to always unconditonally append the above
magic pathspec internally when running "git clean", which would mean
* Existing projects and users' repositories will see no behaviour
change, because they are unaware of the "precious" attribute.
* People who learn the new feature can start using the "ignored but
precious" class, without any need for transition period.