Re: [PATCH] optionally disable overwriting of ignored files
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 22, 2010, 07:25 UTC
- Message-ID
- <7viq335ct0.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20100821080512.GA30141@localhost>
Clemens Buchacher <drizzd@aon.at> writes:
Show 6 quoted lines
> I understand your point. But this is actually a great example. I > have a bunch of such tests, which are not in shape for upstream, > but I want to keep them around anyways (and run them). Do you > really think that an untracked test which was added to > .git/info/exclude should be considered trashable? If it were a > generated file, it would have been added to .gitignore.
I agree that in such a workflow to keep untracked tests around, they should not be considered trashable. But more importantly, as I have already said, adding your untracked tests to exclude is a wrong thing to do.
Traditionally (think "git status" output without "-s") the way to remind oneself that some day these paths need to be added when they are ready has been to keep them untracked but _not_ ignored, so that they will be listed in the output.
Quite contrary to what you earlier said in another message, adding such a path that is not trashable does defeat the point of the "ignore" mechanism.