Re: [PATCH 0/9] worktree: fix bugs and broaden --force applicability
- From
Ramsay Jones <ramsay@ramsayjones.plus.com>
- Date
- Aug 30, 2018, 23:49 UTC
- Message-ID
- <c9d51d68-c7ae-64f9-b3e9-a72f33c5afc3@ramsayjones.plus.com>
- In-Reply-To
- <xmqqva7r4nof.fsf@gitster-ct.c.googlers.com>
On 30/08/18 21:14, Junio C Hamano wrote:
Show 15 quoted lines
> Jeff King <peff@peff.net> writes:
>
>> I suppose so. I don't think I've _ever_ used distclean, and I only
>> rarely use "clean" (a testament to our Makefile's efforts to accurately
>> track dependencies). I'd usually use "git clean" when I want something
>> pristine (because I don't want to trust the Makefile at all).
>
> I do not trust "git clean" all that much, and pre-cleaning with
> "make distclean" and then running "git clean -x" has become my bad
> habit. I jump around quite a bit during the day, which would end up
> littering the working tree with *.o files that are only known to one
> but not both of {maint,pu}/Makefile's distclean rules. I even do
> "for i in pu maint master next; do git checkout $i; make distclean; done"
> sometimes before running "git clean -x" ;-)
> 'git clean -x' always removes _way_ more than I want it to - in particular, I lost my config.mak more than once.
So, no I don't trust it. ;-)
ATB, Ramsay Jones