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

Windows: include= and exclude= containing '/' will also match filenames that are written using '\'

Browse source 
And vice-versa, but it's better to use '/' for portability.

Notably, standardPreferredContent contains "archive/*" and that might not
match if the filename ends up coming in with the slashes the other way
around.
This commit is contained in:
Joey Hess 2020-12-15 12:39:34 -04:00
parent e914cb0777
commit 6b13574827
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
7 changed files with 49 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/drop_claims_that_content_is_required___40__8.20201127__41__/comment_3_9f0415b3945ee80698b5ee50351f1a5c._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2020-12-15T16:16:21Z"
content="""
Hmm, yes preferred content expressions on windows ought
to let `/` be used and still match on `\`. (And vice-versa, although then
the preferred content expression is windows-specific.)
I've implemented that now.
"""]]