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

akley wrote: > 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 >> ex

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

s git Expected result: commit 09357db3a29909c3498143b0d06989e00f5e2442 Author: John Cheng Date: Sun Jan 14 10:57:01 2018 -0800 ... Actual result: Suppose that cygwin git is specified, the result becomes: exit status 128 fatal: ambiguous argument '@u': unknown revision or path not in

Re: Misleading documentation for git-diff-files (diff-filter)

Thanks for the clarification! I also didn't realize that diff-files -R will show added files. You learn something new everyday ;) On Thu, Jan 4, 2018 at 11:09 AM, Junio C Hamano wrote: > Jeff King writes: > >> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt >> index

Re: Misleading documentation for git-diff-files (diff-filter)

some trial and error, I found that git-ls-files gave me what I needed. However, I wanted to point out why I initially believed git-diff-files with show "added files". Think of this more as user feedback. On Wed, Jan 3, 2018 at 3:53 PM, Junio C Hamano wrote: > John Cheng writes: > &

Misleading documentation for git-diff-files (diff-filter)

I originally asked this question on stackoverflow (https://stackoverflow.com/q/48039277). I wanted to know if git diff-files shows files that are not in the index but are in the working tree. The documentation says you can supply --diff-filter=A, which will select file "that are added". However, g