From: Sergey Andreenko <andreenkosa@gmail.com>
To: git@vger.kernel.org
Subject: issue: strange `git diff --numstat` behavior.
Date: Fri, 12 Oct 2018 11:23:28 -0700 [thread overview]
Message-ID: <CAD1gVxMg0ZiKqFABrnwt0v_=wr2X_3ErkR92RmCAtFQnuM+L5w@mail.gmail.com> (raw)
git diff –numstat FOLDER1 FOLDER2 works strange when run from a git
controlled folder.
The output shrinks some symbols in the diff file paths.
For example:
Create a folder and call git init, for example: `C:\test`.
mkdir C:\test
cd C:\test
git init
Create two folders with to diff. For example: ` C:\diff`, `C:\base`
and put a file in them with a diff (for example `1.txt` with `1` in
base and `1.txt` with 2 in diff).
mkdir C:\base
mkdir C:\diff
echo. 12>C:\base\1.txt
echo 13>C:\diff\1.txt
Run git diff:
pushd C:\
git.exe diff --numstat "C:\diff" "C:\base"
Output will be:
1 1 "C:\\diff/1.txt" => "C:\\base/1.txt"
Now move into C:\test and run it again:
pushd C:\test
git.exe diff --numstat "C:\diff" "C:\base"
1 1 "C:\\diff/1.txt" => "C:\\base/1.txt"
Now create a folder in `C:\test`, for example `one`:
mkdir one
cd one
git.exe diff --numstat "C:\diff" "C:\base"
output will be:
0 1 {iff => ase}/1.txt
So (folder_name_length) symbols were cut from the path (“C:\\d” and “C:\\b”).
Is any way to avoid that? I have checked several git versions and they
all do the same.
Commands to repro:
mkdir C:\test
cd C:\test
git init
mkdir C:\base
mkdir C:\diff
echo. 12>C:\base\1.txt
echo 13>C:\diff\1.txt
pushd C:\
git.exe diff --numstat "C:\diff" "C:\base"
pushd C:\test
git.exe diff --numstat "C:\diff" "C:\base"
mkdir one
cd one
git.exe diff --numstat "C:\diff" "C:\base"
Best Regards,
Sergey Andrenko
next reply other threads:[~2018-10-12 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 18:23 Sergey Andreenko [this message]
2018-10-13 8:13 ` issue: strange `git diff --numstat` behavior Junio C Hamano
2018-10-18 18:38 ` [PATCH] diff: don't attempt to strip prefix from absolute Windows paths Johannes Sixt
2018-10-18 18:49 ` Stefan Beller
2018-10-18 19:11 ` Johannes Sixt
2018-10-19 16:58 ` [PATCH v2] " Johannes Sixt
2018-10-19 17:04 ` Stefan Beller
2018-10-19 1:34 ` [PATCH] " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD1gVxMg0ZiKqFABrnwt0v_=wr2X_3ErkR92RmCAtFQnuM+L5w@mail.gmail.com' \
--to=andreenkosa@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.