From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 01C891F4B4 for ; Mon, 21 Sep 2020 22:46:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728000AbgIUWqK (ORCPT ); Mon, 21 Sep 2020 18:46:10 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:51548 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727447AbgIUWqK (ORCPT ); Mon, 21 Sep 2020 18:46:10 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id DAC5070616; Mon, 21 Sep 2020 18:46:07 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=ntk1aq+bCi1x33jwMwEzLwcGXGA=; b=CzlnuJ 264lwjTXe26M/VPUmh/40LztHykn/1lv5vdU0M8frpCozw4tqOKDZy0qtkAPPB6y teVOQMl23owXHibAuQLpkQytp1s58Y9OSRVU6t01kTAgFTN7gdz00yxgxvXfXnzH 8d119GAhzfK71b7YeeY0avLuCTAGSvRoMcZww= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=SyTVZGxXdcOaWfS9eZIHlXl4+MJ9nmwP MrzD9fsh2C9ceICjWPZe9TvYdMYVNLehQH++BTfnTC2KPev+Ciax8OQ4/IcaZ2dZ cKxdNkO5JStl3l8hq2HgFKxUZCLlyJCNhoCAAzUsv48bL4aMpvHUUwlspwcdj3Kd gqzkSv/QNuk= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id CE15D70613; Mon, 21 Sep 2020 18:46:07 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.75.7.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 1DD9F70612; Mon, 21 Sep 2020 18:46:07 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Johannes Schindelin Cc: Johannes Schindelin via GitGitGadget , git@vger.kernel.org Subject: Re: [PATCH] cmake: ignore generated files References: Date: Mon, 21 Sep 2020 15:46:06 -0700 In-Reply-To: (Johannes Schindelin's message of "Sun, 20 Sep 2020 19:15:01 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 3C8FB50C-FC5C-11EA-A62C-2F5D23BA3BAF-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Johannes Schindelin writes: >> What I am hearing here is that people with CMake & VS use "git clean >> -dfx" when they want to go back to the pristine state, unlike those >> who use "make distclean", and there is nothing to adjust for newly >> discovered crufts we are leaving on the filesystem. > > Yes, that is my understanding. I do not know if you have read other messages in the thread, but my current understanding of what we learned in this thread [*1*] is that those who use CMake, especially in a tree like ours that has its own Makefiles, (sh|w)ould create a throw-away directory and run build there, so even "git clean -dxf" is not part of their "clean" procedure. [Footnote] *1* https://lore.kernel.org/git/20200919004030.GB1837@danh.dev/