Re: cygwin git and golang: how @{u} is handled

Hi Phillip, Thanks for pointing me to the github issue. I've added my comments to it. For my particular issue, it was resolved by setting "CYGWIN=noglob" as an environment variable. Hopefully it resolves Robert's problem as well. On Sun, Jan 21, 2018 at 3:43 PM, Philip Oakley

Re: cygwin git and golang: how @{u} is handled

From: "John Cheng" I am experiencing a strange behavior and I'm not certain if it is a problem with golang or the cygwin version of git. Steps to reproduce: Use golang's os/exec library to execute exec.Command(os.Args[1],"log","@{u}") // where os.Args[1] is either cygwin

Re: cygwin git and golang: how @{u} is handled

On Sun, Jan 21 2018, John Cheng jotted: > Actual result: > Suppose that cygwin git is specified, the result becomes: > exit status 128 fatal: ambiguous argument '@u': unknown revision or > path not in the working tree. Given that: $ git log @{x} fatal: ambiguous argument '@{x}':

cygwin git and golang: how @{u} is handled

I am experiencing a strange behavior and I'm not certain if it is a problem with golang or the cygwin version of git. Steps to reproduce: Use golang's os/exec library to execute exec.Command(os.Args[1],"log","@{u}") // where os.Args[1] is either cygwin git or Windows git Expected result: commit