Adina Wagner
Adina Wagner
Linking #6366
this was done in https://github.com/datalad/datalad/pull/6861
Looks like this failed to auto-close. Closing as a fix was merged a while ago.
I have pushed a commit rephrasing the layout section into something that I feel is more pragmatic/non-technical and less vaguely scary. It would be nice to get this vetted by...
ugh, it seems so I guess, at least with ``-l debug``. A normal clone shows completely fine progress bars. a debug log of a clone looks like this: ``` (gooyey)...
> so, we should prevent submodule names, paths, and urls to start with - and if detected -- error out, correct? I re-read a bit into this, and I think...
The verdict from the call was mixed. We acknowledged that there is no vulnerability for DataLad users, since we do not at all rely on git's submodule implementation. However, DataLad...
This was fixed in #6891
> Is there a way to check that datalad-next is available and linked with datalad correctly within my virtual environment? If you run ``datalad --help`` you should see one section...
Yarik said: If he doesn't get to it in the next week, feel free to close