Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"git-meta log -p" appears inconsistent with "git meta diff" #710

Open
rgeary19 opened this issue Jun 17, 2019 · 3 comments
Open

"git-meta log -p" appears inconsistent with "git meta diff" #710

rgeary19 opened this issue Jun 17, 2019 · 3 comments
Labels
bug log issues with

Comments

@rgeary19
Copy link

rgeary19 commented Jun 17, 2019

The -p option to git meta log should list the changes to the files committed. However, instead it shows you the changes to the submodule SHAs, eg.

@@ -1 +1 @@
-Subproject commit ad227241dcd754d2cebf79ef5f170c5920383c0e
+Subproject commit e5232a12bf1c70f404ff91466b8751e491e7c7c4

To get the expected behavior I can add the flag --submodule=diff. However this is unexpected as the purpose of git meta is to pretend there is no submodules.

@petroseskinder
Copy link
Contributor

@rgeary19 this seems like an issue of expectations.

Was it an intentional decision for git meta log -p to not pass --submodule=diff by default, @bpeabody @jhedwardyang @novalis @abliss?

I have had similiar issues with git meta diff. At some point, I had to pass --submodule=diff if I wanted it to display the diff in each submodule.

@novalis
Copy link
Contributor

novalis commented Jun 20, 2019

I agree with this, but it's a bit tricky (in part because one doesn't always have the necessary submodules open). Happy to review a patch.

@bpeabody
Copy link
Contributor

It was not a conscious decision to not pass --submodule=diff; there is a set of commands that are automatically forwarded to vanilla Git. We explicitly went back and made git meta diff as a special case pass in --submodule=diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug log issues with
Projects
None yet
Development

No branches or pull requests

4 participants