mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

remove addition

Browse source 
I understand and sympathize with why this was added here, but the fact
is that this kind of warning is clutter that is going to make it harder
to understand this man page overall; this is not the place to document
internal implementation details of the format of URL keys and more than
it would be the place to document how WORM keys mangle and truncate
filenames, or how the extension of a SHAnE key is chosen. I see that
it did get documented better in backends.mdwn, which is a good place
to document it.

The chance that someone is going to have the same misunderstanding and
happen to see this warning does not justify confusing everyone else
with a warning that is really out of place in this documentation.
This commit is contained in:
Joey Hess 2018-10-16 11:00:22 -04:00
parent 6dd31233e8
commit 8211f6bb87
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/git-annex-examinekey.mdwn
View file

@ -28,10 +28,6 @@ that can be determined purely by looking at the key.
Also, '\\n' is a newline, '\\000' is a NULL, etc.
Note that it is not possible to extract the URL from a key created by the
URL backend: parts of longer URLs may be represented in the key by a
checksum.
* `--json`
Enable JSON output. This is intended to be parsed by programs that use