You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
If a git submodule is present (there is a .gitmodules file) in a git repository, svn access to that repository works fine for initial checkout, but "svn up" reports it has fetched the new commit and... nothin'. It's present in the .svn folder but none of the new changes show up in the working directory.
If I remove the git submodule from the git repository and try again... everything works great.
The text was updated successfully, but these errors were encountered:
To be clear, the entire "main" repository that happens to have at least one submodule in it exhibits this problem. Not just the folder that comes from a git submodule.
boutell
pushed a commit
to punkave/symfony1
that referenced
this issue
Jan 25, 2015
If a git submodule is present (there is a .gitmodules file) in a git repository, svn access to that repository works fine for initial checkout, but "svn up" reports it has fetched the new commit and... nothin'. It's present in the .svn folder but none of the new changes show up in the working directory.
If I remove the git submodule from the git repository and try again... everything works great.
The text was updated successfully, but these errors were encountered: