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

devblog

Browse source
This commit is contained in:
Joey Hess 2018-09-20 16:23:17 -04:00
parent 1d1054faa6
commit ef3f33e40b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/devblog/day_521__newlines_in_filenames.mdwn Normal file
View file

@ -0,0 +1,21 @@
Unix would be better if filenames could not contain newlines. But they can,
and so today was spent dealing with some technical debt.
The main problem with using git-annex with filenames with newlines is that
`git cat-file --batch` uses a line-based protocol. It would be nice if that
were extended to support `-z` like most of the rest of git does, but I
realized I could work around this by not using batch mode for the rare
filename with a newline. Handling such files will be slower than other
files, but at least it will work.
Then I realized that git-annex has its own problems with its `--batch`
option and files with newlines. So I added support for `-z` to every batchable
command in git-annex, including a couple of commands that did batch input
without a `--batch` option.
Now git-annex should fully support filenames containing newlines, as well
as anything else. The best thing to do if you have such a file is to
commit it and then `git mv` it to a better name.
Today's work was sponsored by Trenton Cronholm
[on Patreon](https://patreon.com/joeyh).