On Tue, May 5, 2015 at 12:49 AM, Johannes Schindelin <johannes.schindelin@xxxxxx> wrote: > Hi Robert, > > On 2015-05-04 22:21, Robert Dailey wrote: > >> Since I am not a linux user, I have implemented this feature against >> the Git for Windows fork of git. I am not able to verify changes if I >> make them directly against the Git repository. > > That is why I worked so hard on support of Vagrant: https://github.com/msysgit/msysgit/wiki/Vagrant -- in short, it makes it dead easy for you to set up a *minimal* Linux VM inside your Git SDK and interact with it via ssh. > > With the Vagrant solution, you can easily test Linux Git even on Windows. > > Ciao, > Johannes At the moment I have a "half-ass" patch attached. This implements the feature itself. I'm able to test this and it seems to be working. Please note I'm a C++ developer and straight C / Bash are not my strong suits. I apologize in advance for any mistakes. I am open to taking recommendations for corrections. I'm not sure how I can verify the feature in a unit test. In addition to learning bash scripting well enough to write the test, I am not sure how to use git to check for the additional commits. Plus the repo for the test will need to handle a submodule change to a merge commit as well. Any advice on setting up a good test case for this? What conditions should I check for, as far as log output goes?
Attachment:
0001-Add-full-log-option-to-diff.submodule.patch
Description: Binary data