diff options
author | 2015-11-27 19:16:53 +0000 | |
---|---|---|
committer | 2015-11-27 19:16:53 +0000 | |
commit | 8d312249580f28f253b9587283c60c1e371dcabb (patch) | |
tree | 6cda536e48211bc13ed70c68f74101fe0e0df711 | |
parent | 47a5b33a1f6632e60a61e429aecb4875ddad97e1 (diff) |
-rw-r--r-- | doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn b/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn new file mode 100644 index 000000000..fec502b9e --- /dev/null +++ b/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn @@ -0,0 +1,32 @@ +### Please describe the problem. + +git annex reports progress the same when when stdout is a terminal or not. +This is fine when stdout is actually a terminal, but produce lots of annoying characters when stdout is just a regular file. +This is problematic mostly when running git-annex with cron. + +### What steps will reproduce the problem? + +git annex copy --to myrepo > log + +then look at the content of log. + +### What version of git-annex are you using? On what operating system? + +5.20151019 + +Mac OS X 10.10.5 +Ubuntu 14.04 + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + + |