File: comment_19_89d532a5013af24f15a0d003cbfbab25._comment

package info (click to toggle)
git-annex 7.20190129-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 56,292 kB
  • sloc: haskell: 59,105; sh: 1,255; makefile: 225; perl: 136; ansic: 44
file content (13 lines) | stat: -rw-r--r-- 515 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
[[!comment format=mdwn
 username="joey"
 subject="""re: WHEREIS -- is it better to just report failure to avoid duplicates?"""
 date="2015-09-09T21:03:13Z"
 content="""
There's no point in implementing WHEREIS if it's going to reply with the
same values that are passed to SETURIPRESENT.

Some special remotes may not need to use SETURIPRESENT to work at
all, and yet storing data on the remote makes it available from some public
url. This is the kind of situation where it makes sense to implement
WHEREIS.
"""]]