diff options
author | yarikoptic <yarikoptic@web> | 2017-02-06 00:49:28 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2017-02-06 00:49:28 +0000 |
commit | f026f717b35c94bdb70e4948b80d49c8c467701f (patch) | |
tree | 530cbcc9b609c974932c71b66e4f4f73742120b4 /doc | |
parent | 96e5b4bd5156ea9043ccc069c8dde369c9fdc19e (diff) |
initial thoughts
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/be_able_to_refer_to_remotes_by_uuid.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/todo/be_able_to_refer_to_remotes_by_uuid.mdwn b/doc/todo/be_able_to_refer_to_remotes_by_uuid.mdwn new file mode 100644 index 000000000..35c1d8cd9 --- /dev/null +++ b/doc/todo/be_able_to_refer_to_remotes_by_uuid.mdwn @@ -0,0 +1,3 @@ +in light of https://github.com/datalad/datalad/issues/1259 (conflicting remote names) I wondered if both initremote and enableremote (and probably others) should acquire ability to set/refer to remotes by their UUIDs instead of relying purely on name which is not guaranteed to be unique. + +[[!meta name=yoh]] |