diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-01-01 16:07:38 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-01-01 16:07:38 -0400 |
| commit | 782956d7fbfd420d08c212538df887f5b22eb4a6 (patch) | |
| tree | e05bcc8b843e079de04470e5a12040779fcbbcb3 | |
| parent | f755deb1c6059857a375db2b68b5d20886fafbbe (diff) | |
response
| -rw-r--r-- | doc/git-annex-importfeed/comment_2_25d4ed016e98609066597a8d2b956f87._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/git-annex-importfeed/comment_2_25d4ed016e98609066597a8d2b956f87._comment b/doc/git-annex-importfeed/comment_2_25d4ed016e98609066597a8d2b956f87._comment new file mode 100644 index 000000000..206dab711 --- /dev/null +++ b/doc/git-annex-importfeed/comment_2_25d4ed016e98609066597a8d2b956f87._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2016-01-01T20:04:02Z" + content=""" +All spaces and punctuation (other than '.') and other wacky stuff are replaced with +'_' when git-annex builds a filename from some untrusted source like a +feed. + +I think it makes sense to do that even for '-', at least if it's at the +start of a filename. "--force" is not a filename you want to let a feed +inject into your work tree. I could perhaps be convinced to let '-' +elsewhere in the filename through unmunged, but simplicity and consistency +suggests it's just as good to always munge it. +"""]] |