vibhatha commented on PR #13232: URL: https://github.com/apache/arrow/pull/13232#issuecomment-1144877608
> > ``` > > git submodule update --init --recursive > > # Note, at this point you will have some staged changes that you want to commit and > > # some unstaged changes that you do not want to commit. So do not run `git add` > > git commit -m "Restored submodules" > > git submodule update > > # At this point you should have no unstaged or staged changes and the submodules should > > # be in sync with master > > ``` > > > I tried this just in case but, as expected, git said there was nothing to commit after `git submodule update --init --recursive`. As [noted above](https://github.com/apache/arrow/pull/13232#issuecomment-1143327614), the issue is not in my local repo, which is in a good state. Though not probable, the issue might be in GitHub or how it presents this PR, which doesn't look consistent (see links in my note). > > > To move forward, if you're not happy with the state of the `testing` submodule in this PR, I'd start a fresh one because I don't seem to have a way to fix this one. May be this could help: https://stackoverflow.com/questions/8191299/update-a-submodule-to-the-latest-commit Also I guess, you may need to remove the committed files first and then checkout the version of submodule used by the project. In that case you may not need to commit any things. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
