[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PROPOSAL: Move to git, now that bzr is no longer a req.

From: Óscar Fuentes
Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req.
Date: Fri, 03 Jan 2014 21:37:08 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

> You wanna bet?  I prefer an environment where I know what can and what
> cannot happen.

So yo do worry about hypothetical, unknown problems (unknown unknowns).
That's fine, but hardly a serious argument against MSYSGit.

>> Those rules affects a given process. That means that the fact that
>> process `foo' loaded certain DLLs does not affect which DLLs are loaded
>> for process `bar', even when `bar' is executed from `foo'.
> I invoked 'make' from the Bash that was installed by msysgit.  That
> 'make' hang.  The same command runs just fine from the MSYS Bash I use
> for configuring and building packages.  That's a fact.  I think I know
> the reasons, but if you want to disagree and live dangerously, that's
> fine by me.

IIUC you invoked MSYS `make' from MSYSGit `bash'. As I said multiple
times, that's not expected to work.

>> It would be quick enough to run some common git commands from MSYS shell
>> to see if it works: clone, pull, status, log...
> I already tried, see above.

No, you didn't. As git.exe does not depend on MSYS.dll, the problems you
experienced with `make' shouldn't happen. And, indeed, invoking MSYSGit
git.exe from a MSYS terminal worked fine for the commands I mentioned


reply via email to

[Prev in Thread] Current Thread [Next in Thread]