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
Now (0.12.0rc4.dev5) it is easier on eyes but without consideration of the "context" from which the command was called, reported paths within subdatasets could be confusing, wrong, or misleading:
However, at this point I am closing it at a time of ~600 open issues, in an attempt to regain control over the issue tracker. This particular issue was posted more than 6 months ago, has not received a single response, and does not describe an immediate software defect. Closing this issue does not imply that it is not relevant. If any reader objects the closing of this issue, please feel more than free to reopen it with an update on how it is relevant for the current state of the project, and which concrete actions to address it are ongoing or planned.
if before (0.11.x) it was suboptimal due to full paths:
Now (0.12.0rc4.dev5) it is easier on eyes but without consideration of the "context" from which the command was called, reported paths within subdatasets could be confusing, wrong, or misleading:
not to mention that I am not sure what "add(ok): subds (file)" means since I do not have
subds
file in this example.The text was updated successfully, but these errors were encountered: