recursive subrepo - is this supposed to work?

ingydotnet / git-subrepo

MIT License

3.29k stars 271 forks source link

recursive subrepo - is this supposed to work? #482

Open hholst80 opened 4 years ago

hholst80 commented 4 years ago

om@hholst-lt:~/Documents/qwer$ git subrepo clone ../PVC/DeploymentA/ DeploymentA
Subrepo '../PVC/DeploymentA' (feature) cloned into 'DeploymentA'.
om@hholst-lt:~/Documents/qwer$ git subrepo clone ../PVC/ServiceA/ DeploymentA/ServiceA
Subrepo '../PVC/ServiceA' (master) cloned into 'DeploymentA/ServiceA'.
om@hholst-lt:~/Documents/qwer$ git subrepo status
1 subrepo:

Git subrepo 'DeploymentA':
  Remote URL:      ../PVC/DeploymentA
  Upstream Ref:    fc4ec33
  Tracking Branch: feature
  Pulled Commit:   fc4ec33
  Pull Parent:     f6f0e63

admorgan commented 4 years ago

I don't know how I missed this, sorry it has taken so long to reply. Yes this should work, actually it does work if you look in the location, it is the status command that is miss behaving this issue has been reported in other ways. You can still work on the recursive repo. I am going to try to find some time this weekend to get to the root of this and release 0.4.2.

Chardrazle commented 3 years ago

Just stumbled across this. As noted, it works fine, just appears to be the status display. For us, we subrepo google-breakpad, but (for Linux) this requires the https://chromium.googlesource.com/linux-syscall-support to sit under .../src/third_party/lss/ That one does not show in the status.