Re: git 2.8.3 spurious output

Warren Young etr-usa.com> writes: > Incidentally, I see that I forgot to fix a /c -> /cygdrive/c in the script > I posted. (I normally run with cygdrive mounted at the root, and write my > scripts accordingly.) reminder - /proc/cygdrive/c/ works on all systems - saves worrying about it

Re: git 2.8.3 spurious output

On Jun 9, 2016, at 1:52 AM, Cufi, Carles wrote: > >> I prefer to use Cygwin most of the >> time, then run a âmingwâ script I wrote to temporarily shift my Cygwin >> environment to MinGW mode: > > This sounds like a very good idea, but the problem is that sometimes I

Re: git 2.8.3 spurious output

Hi there, > On Jun 8, 2016, at 8:19 AM, Cufi, Carles wrote: > > > > So what's the better way of fixing this? Making /mingw/bin/gettext.sh > have UNIX line endings or replacing it with the proper Cygwin gettext.sh > that I seem to be missing? > > Donât try to mix the Cygwin and MinGW build

Re: git 2.8.3 spurious output

Cufi, Carles writes: >> In general, however, it seems to me that you're asking for trouble by >> having MinGW binaries in your path while working in Cygwin. > > Yep, I want to do that but the problem is that Cygwin inherits the > global PATH from Windows and MinGW is present there. I guess I could

Re: git 2.8.3 spurious output

> On 6/8/2016 10:19 AM, Cufi, Carles wrote: > > On 6/8/2016 9:57 AM, Cufi, Carles wrote: > Hi there, > > On 6/8/2016 5:35 AM, Cufi, Carles wrote: > Hi, > > When running git 2.8.3 with certain of its commands (submodule for > example) I get spurious output on the terminal: > > cacu

Re: git 2.8.3 spurious output

On Jun 8, 2016, at 8:19 AM, Cufi, Carles wrote: > > So what's the better way of fixing this? Making /mingw/bin/gettext.sh have > UNIX line endings or replacing it with the proper Cygwin gettext.sh that I > seem to be missing? Don’t try to mix the Cygwin and MinGW build systems. Having MinGW

Re: git 2.8.3 spurious output

On 6/8/2016 10:19 AM, Cufi, Carles wrote: On 6/8/2016 9:57 AM, Cufi, Carles wrote: Hi there, On 6/8/2016 5:35 AM, Cufi, Carles wrote: Hi, When running git 2.8.3 with certain of its commands (submodule for example) I get spurious output on the terminal: cacu ~/src/nordic/gh/pc-ble-driver-py

Re: git 2.8.3 spurious output

> On 6/8/2016 9:57 AM, Cufi, Carles wrote: > Hi there, > > On 6/8/2016 5:35 AM, Cufi, Carles wrote: > Hi, > > When running git 2.8.3 with certain of its commands (submodule for > example) I get spurious output on the terminal: > > cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule

Re: git 2.8.3 spurious output

On 6/8/2016 9:57 AM, Cufi, Carles wrote: Hi there, On 6/8/2016 5:35 AM, Cufi, Carles wrote: Hi, When running git 2.8.3 with certain of its commands (submodule for example) I get spurious output on the terminal: cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule deinit . ': not a

Re: git 2.8.3 spurious output

Hi there, > On 6/8/2016 5:35 AM, Cufi, Carles wrote: > Hi, > > When running git 2.8.3 with certain of its commands (submodule for > example) I get spurious output on the terminal: > > cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule deinit . > ': not a valid identifiertext.sh:

Re: git 2.8.3 spurious output

On 6/8/2016 9:45 AM, Ken Brown wrote: On 6/8/2016 5:35 AM, Cufi, Carles wrote: Hi, When running git 2.8.3 with certain of its commands (submodule for example) I get spurious output on the terminal: cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule deinit . ': not a valid

Re: git 2.8.3 spurious output

On 6/8/2016 5:35 AM, Cufi, Carles wrote: Hi, When running git 2.8.3 with certain of its commands (submodule for example) I get spurious output on the terminal: cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule deinit . ': not a valid identifiertext.sh: line 88: export:

git 2.8.3 spurious output

Hi, When running git 2.8.3 with certain of its commands (submodule for example) I get spurious output on the terminal: cacu ~/src/nordic/gh/pc-ble-driver-py (master) $ git submodule deinit . ': not a valid identifiertext.sh: line 88: export: `displaypath Cleared directory '' ': not a valid