From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Radon Rosborough Newsgroups: gmane.emacs.devel Subject: Re: Why does make run git? Date: Thu, 3 Aug 2017 13:02:04 -0700 Message-ID: References: <83bmo00yw7.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1501790619 1264 195.159.176.226 (3 Aug 2017 20:03:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 3 Aug 2017 20:03:39 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org, tino.calancha@gmail.com To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 03 22:03:32 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddMLD-0008C5-Qq for ged-emacs-devel@m.gmane.org; Thu, 03 Aug 2017 22:03:31 +0200 Original-Received: from localhost ([::1]:47058 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddMLI-0000TD-6Q for ged-emacs-devel@m.gmane.org; Thu, 03 Aug 2017 16:03:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48161) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddMKa-0000Sl-Ds for emacs-devel@gnu.org; Thu, 03 Aug 2017 16:02:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddMKZ-0001G6-HU for emacs-devel@gnu.org; Thu, 03 Aug 2017 16:02:52 -0400 Original-Received: from mail-lf0-x229.google.com ([2a00:1450:4010:c07::229]:34036) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ddMKW-0001BT-P3; Thu, 03 Aug 2017 16:02:49 -0400 Original-Received: by mail-lf0-x229.google.com with SMTP id g25so10533349lfh.1; Thu, 03 Aug 2017 13:02:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uir6l2l5L15OWc4YTNyCkSvGOih3isOns8QbV7dxKT8=; b=NIk+AKsMSlFAFucuksbgKf39IakAcOlscUMUWREykJq5ynhOCyQWDmCTZYIjWL6xxF btJxDIZ5lWy8DhHEZl602futfcHfx7a+GOL/jD/u8CmRUvRy+JVgwrgHk/wnOQN8vrIg 2tmo0mbS1qRngnsbDMJ8OQvsNcDfOTxIyD6hIJnTxoNnsXL0vPXz6CDoDS/mZPgnknIB Kf3xgKvLOzc9ujkH5FUx8eBEYVkki3lPnRZYErTKALvao4bl8yTeIjf26ZgM5sgTVGxU nqqhAaWcrlqgn/a5dH1Oba2Jp1jpqI9rhhR2YgdzJY1E2AH8WJPAXROoOKu2VjlrX+F5 jnmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uir6l2l5L15OWc4YTNyCkSvGOih3isOns8QbV7dxKT8=; b=ZNtmOUmQP88XuzY31zWWtgXwFGpkCvnfAZ1l9hqboJ+TbPwvq6mu8ecnORx/cBkOwi LSF7PlzAWw2gW9xzrxZzyATzSQ++dTDCqLoGjHqteF9VOgRO6WMZGRQMbeY8r3fJQXm0 BWdLxeJnVp0iG55fsSQys6zSF5urdVeoxsZb8IGhglzwLgmC9pl4AVjY/b3oP1LHv9NS mDX3fBeI8lZtv1Osq1DXrQJTK9DU78O8uHFmFcIFCzeBB4CWJtt9w7PN0RM6Ja4KJrS0 n0acAJwtOt0SC/tDZOCyEOls/RiAj8/PAEGh840i59xg/iKkxUC8AF83UFrRtPSpYkPO TMzQ== X-Gm-Message-State: AHYfb5iVpl05CsJgNRbc/fUNK7YoDdLzfLOhbbaNLRlSlejy/r5u4BR6 5HgQjs9QbBUedHFnyf5HrbI0lZiUFv0DIH4= X-Received: by 10.25.228.89 with SMTP id b86mr905888lfh.218.1501790565443; Thu, 03 Aug 2017 13:02:45 -0700 (PDT) Original-Received: by 10.46.64.86 with HTTP; Thu, 3 Aug 2017 13:02:04 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4010:c07::229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:217273 Archived-At: > We could make it a documented Emacs facility, > which could be used by any repository, and all front-ends ought > to call it. I don't object, but this sounds a little bit like overkill to me. This would be a significant amount of added complexity (e.g. notifying all known authors of version-control packages [maybe not that many?] and hoping they incorporate supporting changes; dealing with safety [is safe-local-variable-values enough?]; working out the appropriate scope [is this just for Git? can you also run arbitrary shell commands?]; designing an interface that will cover all common use cases; making sure that this doesn't impact performance; deciding whether to override existing configuration and hooks; etc.), and it still doesn't really fix the problem since plenty of people will just use Git directly. I'd vote for leaving the situation as-is, since there's no general way to prevent people from using Git without first configuring it. The "right" solution is to not rely on the local Git configuration for anything mission-critical. OTOH, since this is a relatively common problem, maybe somebody has already invented a general-purpose solution. In that case perhaps Emacs should support that standard. I don't think Emacs should create its own standard in this case.