Do check the history simplification which may means some things you may expect are not actually treated that way.
Do you have the actual commands & results (copy & paste, with redactions marked) What specific software (both Git & Operating system) versions are you using in the cases. You say it works on Win10. Is that WSl & (linux) Git; or Git for Windows (again which version)? Are any of the repositories on server or network drives (i.e what is the network connectivity - some network software does not always pass the correct status bits, and some Git versions have interesting ideas about handling mode bits for compatibility). What is the actual "invalid" result for the full diff of the --name-stat'ed file(s) (is it mode bits, or file content difference!) Can you create a simplified reproducible version (maybe even the fast-export --anonymize) finally, not knowing Rocket Port, could this https://forum.rocketsoftware.com/t/important-notice-for-users-of-the-rocket-port-of-git-for-z-os/1102 be part of the issue? Philip On 22/06/2020 17:53, lbd...@gmail.com wrote: > > The scenario is this: > Create a master branch - make updates - add/commit > New branch to branchB - make changes/updates - add/commit > New branch to branch C (from branchB) - make changes/updates - add/commit > > issue git diff --name-status master branchB and all is good > issue git diff --name-status branchB branchC and all is good > issue git diff --name-status master branchC and get invalid results ( > > When I do this on my windows 10 pc everything works and no invalid > results. > > Using Rocket Port of git at git version 2.14.4_zos_b09 > and Windows version at git version 2.17.1 > > Is this a known issue? > > Lionel B. Dyck <sdg>< > Website: https://www.lbdsoftware.com > > "Worry more about your character than your reputation. Character is > what you are, reputation merely what others think you are." - John Wooden > > > > From: git-users@googlegroups.com <git-users@googlegroups.com> On > Behalf Of Philip Oakley > Sent: Saturday, June 20, 2020 5:01 PM > To: Git for human beings <git-users@googlegroups.com> > Subject: [git-users] Re: Git - how to determine what files changes > > > > Do you mean that you simply need to get the direct difference between > A and B. > > > > Or do you mean you want to see hwat changed in A since B was forked, > and like wise what changed in B since that same fork point? > > > > Have a look for the three dot `...` notation to get a fork point and > also the boundary (`<, >`) indications of left side and right side. > > > > Hope that helps for a hint when cross checking with the various man pages. > > > > Philip. > > > On Saturday, June 20, 2020 at 5:12:18 PM UTC+1, lbd...@gmail.com > <mailto:lbd...@gmail.com> wrote: > > Is there a command that will show the files that changed when > changing branches? > > > > I want to have an easy way to tell which files have changed when I > switch from Branch A to Branch B, or vice versa. > > > > This seems to work but I can’t easily tell which files changed in > which branch (or I’m just not seeing it): > > > > git diff --name-status branch1 branch2 > > > > > > Thank you > > > > > > Lionel B. Dyck <sdg>< > Website: https://www.lbdsoftware.com > > "Worry more about your character than your reputation. Character > is what you are, reputation merely what others think you are." - > John Wooden > > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/fd81b1fd-47fc-340f-a9f0-a6ffcb1013d2%40iee.email.
