From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req. Date: Fri, 03 Jan 2014 16:32:46 +0100 Message-ID: <871u0p5bdt.fsf@wanadoo.es> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87fvp6bdd9.fsf_-_@ktab.red-bean.com> <83wqiixqbb.fsf@gnu.org> <20140102172804.GB13245@thyrsus.com> <83vby2xo6x.fsf@gnu.org> <83r48qxg6e.fsf@gnu.org> <87y52y5bau.fsf@wanadoo.es> <83iou1y06o.fsf@gnu.org> <87ha9l5d82.fsf@wanadoo.es> <83txdlw1aw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1388763193 19800 80.91.229.3 (3 Jan 2014 15:33:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 3 Jan 2014 15:33:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 03 16:33:19 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Vz6kQ-0007vT-IK for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2014 16:33:18 +0100 Original-Received: from localhost ([::1]:50357 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz6kQ-0000UU-5T for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2014 10:33:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz6kI-0000UF-E9 for emacs-devel@gnu.org; Fri, 03 Jan 2014 10:33:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vz6kC-0006Gu-Jd for emacs-devel@gnu.org; Fri, 03 Jan 2014 10:33:10 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:36060) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz6kC-0006Gi-EU for emacs-devel@gnu.org; Fri, 03 Jan 2014 10:33:04 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vz6k7-0007No-DH for emacs-devel@gnu.org; Fri, 03 Jan 2014 16:32:59 +0100 Original-Received: from 225.red-81-44-202.dynamicip.rima-tde.net ([81.44.202.225]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jan 2014 16:32:59 +0100 Original-Received: from ofv by 225.red-81-44-202.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jan 2014 16:32:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 42 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 225.red-81-44-202.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:KSZ3EawX+DdRgD/my5LTVlSgb9I= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:167178 Archived-At: Eli Zaretskii writes: >> git.cmd can be used from the command line. > > Did you actually try that, for real? git.cmd sets PATH to include > git's binaries, which include MSYS DLL. This means you cannot use in > the same session any commands that might conflict. E.g., consider > what would happen if you invoke git.cmd from a Makefile, or the other > way around. I tried that, and got stuck and crashing programs. No, > thanks. git.cmd is not meant to permanently set any variable. It is invoked from a shell as `git ' Whatever environment variables it sets are effective only until the command finishes, and for that sole command. As previously mentioned, there is no git.cmd anymore but a git.exe that knows where the other commands are located. >> > No, but some git commands need Bash and shell scripts, and thus invoke >> > MSYS programs that do need the MSYS DLL. >> >> You don't need MSYS on the PATH, so whatever those commands use is an >> interal implementation detail. > > No, it isn't. When MSYS DLL is loaded, any other program that is > linked to that DLL will try to use it -- and will fail if it needs an > incompatible version of that DLL. Therefore, you can't invoke, say, > the MSYS 'make' from the Git Bash shell, or from any Git command. Are you sure about this? Windows allows multiple DLLs with the same names and every application will load one of them as per the effective environment when the application is launched. So if you don't put MSYSGit binary directory on the PATH, its existence shouldn't make a difference for the rest of the system. A different history is if you invoke an MSYS (or Cygwin) executable from MSYSGit, or vice-versa, but that is an improbable scenario (please keep in mind that git.exe is not a MSYS binary, so invoking it from Cygwin/MSYS shouldn't be problematic, at least for the usual git commands.)