Note, in my first paragraph, I should have said "If I have multiple local git repos, and I run `git status -v` on them *concurrently*"... -alex On Sat, Aug 4, 2018 at 2:47 PM, Alexander Mills <alexander.d.mills@xxxxxxxxx> wrote: > If I have multiple local git repos, and I run `git status -v` on them, > sometimes I don't get any stdout for the command. This is highly > reproducible. > > I assume that access more than 1 git repo concurrently on a local > machine is not without errors. However this seems like a huge > limitation or design flaw. > > Is my observation correct? Are there any plans to remove this limitation? > > My use case - I create a lot of developer tools and more than once I > have hit this limitation...I have to create a queue with concurrency > of 1 to run commands on git repos. It's very strange and > counterintuitive to have to do this. > > > -- > Alexander D. Mills > ¡¡¡ New cell phone number: (415)730-1805 !!! > alexander.d.mills@xxxxxxxxx > > www.linkedin.com/pub/alexander-mills/b/7a5/418/ -- Alexander D. Mills ¡¡¡ New cell phone number: (415)730-1805 !!! alexander.d.mills@xxxxxxxxx www.linkedin.com/pub/alexander-mills/b/7a5/418/
