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

moreinfo

Browse source
This commit is contained in:
Joey Hess 2017-10-30 12:19:33 -04:00
parent 81926f638e
commit fb9b4724ba
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/Export_fails_for_files_directly_in_git_repo/comment_1_0077e5e36896116059070e26143f03d0._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-10-30T16:11:42Z"
content="""
More information needed to reproduce this.
Normally adding a "file.txt" would not ever result in its key
containing a space like that. So, it seems to me you must have
already added a file with the same content to the annex, in a
way that caused its key's name to contain a space.
(I guess you're also using v6 mode, that's the only way "git add" would
add the file to git-annex.)
Also note that the limitation on spaces in key names only impacts
exporting to external special remotes, so "exp" must be some kind
of external special remote. (I was not aware of any that
supported exports yet..)
Suggest you `git show a05faa1` and see what key it used, that will
make the above speculations a bit more concrete.
"""]]