From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] cmake: ignore generated files
Date: Fri, 25 Sep 2020 08:40:20 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2009250808000.5061@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqft78i5zd.fsf@gitster.c.googlers.com>
Hi Junio,
On Wed, 23 Sep 2020, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > All I want is for the CMake support to be easier to use, yet we go in the
> > opposite direction: instead of allowing to use CMake under more
> > circumstances (which actually *works*, we just don't have the appropriate
>
> Not, "more", but what you are doing is to ensure it is used at only
> one single place, which is the top-level (and nowhere else, judging
> from the .gitignore additions).
>
> And that is fine---if you were to add .gitignore entries, you cannot
> leave it up to the end-users where the build happens.
>
> So, let's not pretend that you are allowing "more circumstances".
> Forcing a single choice to make things predictable is fine, but
> let's explain it as such, so that people won't be confused into
> thinking that they can follow their experiences gained from using
> CMake in other projects that lets them build in a separate
> directory. The other things in our project, including the
> patterns added to .gitignore with the patch in question, are not set
> up to allow that.
While I respectfully disagree that I force a single choice on anybody, I
do agree that there is value in having one recommended route that is well
supported.
Thanks,
Dscho
next prev parent reply other threads:[~2020-09-25 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 20:37 [PATCH] cmake: ignore generated files Johannes Schindelin via GitGitGadget
2020-09-17 21:49 ` Junio C Hamano
2020-09-18 13:11 ` Johannes Schindelin
2020-09-18 15:28 ` Junio C Hamano
2020-09-18 15:50 ` Đoàn Trần Công Danh
2020-09-18 16:21 ` Junio C Hamano
2020-09-19 0:40 ` Đoàn Trần Công Danh
2020-09-19 0:50 ` Junio C Hamano
2020-09-20 17:37 ` Johannes Schindelin
2020-09-23 15:59 ` Junio C Hamano
2020-09-23 20:27 ` Johannes Schindelin
2020-09-23 20:38 ` Junio C Hamano
2020-09-25 6:40 ` Johannes Schindelin [this message]
2020-09-24 10:34 ` Đoàn Trần Công Danh
2020-09-25 5:02 ` Johannes Schindelin
2020-09-20 17:15 ` Johannes Schindelin
2020-09-21 22:46 ` Junio C Hamano
2020-09-23 13:08 ` Johannes Schindelin
2020-09-24 9:19 ` SZEDER Gábor
2020-09-24 17:11 ` Junio C Hamano
2020-09-23 17:47 ` Junio C Hamano
2020-09-23 17:53 ` 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=nycvar.QRO.7.76.6.2009250808000.5061@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
/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).