74c1e0660b
git -c was already propagated via environment, but need this for consistency. Also, notice it does not use gitAnnexChildProcess to run the transferrer. So nothing is done about avoid it taking the pid lock. It's possible that the caller is already doing something that took the pid lock, and if so, the transferrer will certianly fail, since it needs to take the pid lock too. This may prevent combining annex.stalldetection with annex.pidlock, but I have not verified it's really a problem. If it was, it seems git-annex would have to take the pid lock when starting a transferrer, and hold it until shutdown, or would need to take pid lock when starting to use a transferrer, and hold it until done with a transfer and then drop it. The latter would require starting the transferrer with pid locking disabled for the child process, so assumes that the transferrer does not do anyting that needs locking when not running a transfer.
12 lines
499 B
Markdown
12 lines
499 B
Markdown
When `git annex -c foo.bar` runs git-annex transferrer,
|
|
it does not pass along the settings from -c.
|
|
|
|
(Note that, `git -c foo.bar annex` does propagate the -c. Git does it by
|
|
setting an environment variable, which causes git config to reflect the
|
|
override. The environment variable propagates to child processes.)
|
|
|
|
There are a lot of config settings that impact transfers,
|
|
and some of them might be commonly used at the command line, so something
|
|
needs to be done about this. --[[Joey]]
|
|
|
|
> [[done]]
|