Build report

Start time:
2019-03-24 01:30:01 (CET)
End time:
2019-03-24 11:40:01 (CET)
Duration:
610min 0s
Termination Status:
Error
Schedule full rebuild

Previous builds

latest
2019-03-24 02:10:53 (CET) - 40min 52s
2019-03-23 02:10:59 (CET) - 40min 58s
2019-03-22 02:11:34 (CET) - 41min 33s
2019-03-21 02:13:42 (CET) - 43min 41s
2019-03-20 02:10:54 (CET) - 40min 53s
2019-03-19 02:10:57 (CET) - 40min 56s
2019-03-18 02:10:24 (CET) - 40min 23s
2019-03-17 02:12:39 (CET) - 42min 38s
2019-03-16 02:59:44 (CET) - 89min 42s
2019-03-15 02:09:40 (CET) - 39min 39s

VCS changes

Premake

[01:30:35] make[1]: Nothing to be done for 'all'.
[01:30:35] make[1]: Leaving directory '/srv/www/test.fsfe.org_git/news'
[01:30:35] printf %s\n   '<?xml version="1.0" encoding="utf-8"?><dateset><date day="2019-03-24" /></dateset>' >d_day.en.xml
[01:31:38] touch events/events.sources
[01:31:38] touch tags/tags.sources
[01:31:39] touch donate/thankgnus.sources
[01:31:40] touch at/at.sources
[01:31:42] touch fellowship/index.sources
[01:31:45] touch index.sources
[01:31:46] make: Leaving directory '/srv/www/test.fsfe.org_git'
full log

Makefile

Header

.PHONY: all
PROCESSOR = "/srv/www/test.fsfe.org_git/build/process_file.sh"
PGLOBBER = "/srv/www/test.fsfe.org_git/build/source_globber.sh"
PROCFLAGS = --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org"
INPUTDIR = /srv/www/test.fsfe.org_git
OUTPUTDIR = /srv/www/test.fsfe.org_stage

# cannot store find results in variable because it will result in too many arguments for the shell
# ${INPUTDIR}/tagmap: $(shell find "/srv/www/test.fsfe.org_git" -name '*.[a-z][a-z].xml')
# 	find "/srv/www/test.fsfe.org_git" -name '*.[a-z][a-z].xml' |xargs ${PGLOBBER} ${PROCFLAGS} map_tags >${INPUTDIR}/tagmap

Copy rules

	cp "${INPUTDIR}/freesoftware/support/vnc.png" "${OUTPUTDIR}/freesoftware/support/vnc.png"
all: ${OUTPUTDIR}/freesoftware/support/manual.png
${OUTPUTDIR}/freesoftware/support/manual.png: ${INPUTDIR}/freesoftware/support/manual.png
	cp "${INPUTDIR}/freesoftware/support/manual.png" "${OUTPUTDIR}/freesoftware/support/manual.png"
all: ${OUTPUTDIR}/freesoftware/support/wiki.png
${OUTPUTDIR}/freesoftware/support/wiki.png: ${INPUTDIR}/freesoftware/support/wiki.png
	cp "${INPUTDIR}/freesoftware/support/wiki.png" "${OUTPUTDIR}/freesoftware/support/wiki.png"
all: ${OUTPUTDIR}/sitemap.txt
${OUTPUTDIR}/sitemap.txt: ${INPUTDIR}/sitemap.txt
	cp "${INPUTDIR}/sitemap.txt" "${OUTPUTDIR}/sitemap.txt"

Source copy rules

	cp "${INPUTDIR}/freesoftware/support/support.it.xhtml" "${OUTPUTDIR}/source/freesoftware/support/support.it.xhtml"
all: ${OUTPUTDIR}/source/freesoftware/third-sector/third-sector.en.xhtml
${OUTPUTDIR}/source/freesoftware/third-sector/third-sector.en.xhtml: ${INPUTDIR}/freesoftware/third-sector/third-sector.en.xhtml
	cp "${INPUTDIR}/freesoftware/third-sector/third-sector.en.xhtml" "${OUTPUTDIR}/source/freesoftware/third-sector/third-sector.en.xhtml"
all: ${OUTPUTDIR}/source/work.nl.xhtml
${OUTPUTDIR}/source/work.nl.xhtml: ${INPUTDIR}/work.nl.xhtml
	cp "${INPUTDIR}/work.nl.xhtml" "${OUTPUTDIR}/source/work.nl.xhtml"
all: ${OUTPUTDIR}/source/work.el.xhtml
${OUTPUTDIR}/source/work.el.xhtml: ${INPUTDIR}/work.el.xhtml
	cp "${INPUTDIR}/work.el.xhtml" "${OUTPUTDIR}/source/work.el.xhtml"

XSLT rules

${INPUTDIR}/tools/xsltsl/events-utils.xsl: 
	touch "${INPUTDIR}/tools/xsltsl/events-utils.xsl"
${INPUTDIR}/tools/xsltsl/static-elements.xsl: ${INPUTDIR}/tools/xsltsl/string.xsl
	touch "${INPUTDIR}/tools/xsltsl/static-elements.xsl"
${INPUTDIR}/tools/wikicalendars.xsl: 
	touch "${INPUTDIR}/tools/wikicalendars.xsl"
${INPUTDIR}/fsfe.xsl: ${INPUTDIR}/build/xslt/gettext.xsl ${INPUTDIR}/tools/xsltsl/static-elements.xsl ${INPUTDIR}/tools/xsltsl/tagging.xsl ${INPUTDIR}/build/xslt/fsfe_head.xsl ${INPUTDIR}/build/xslt/fsfe_body.xsl ${INPUTDIR}/build/xslt/fsfe_document.xsl ${INPUTDIR}/build/xslt/fsfe_headings.xsl ${INPUTDIR}/build/xslt/fsfe_localmenu.xsl ${INPUTDIR}/build/xslt/fsfe_nolocal.xsl
	touch "${INPUTDIR}/fsfe.xsl"
${INPUTDIR}/it/it.xsl: ${INPUTDIR}/tools/xsltsl/countries.xsl ${INPUTDIR}/fsfe.xsl
	touch "${INPUTDIR}/it/it.xsl"

XHTML rules

all: ${OUTPUTDIR}/work.uk.html ${OUTPUTDIR}/work.html.uk
${OUTPUTDIR}/work.uk.html: ${INPUTDIR}/work.*.xhtml ${INPUTDIR}/default.xsl ${INPUTDIR}/tools/texts-en.xml ${INPUTDIR}/tools/texts-en.xml  ${INPUTDIR}/tools/menu-global.xml 
	${PROCESSOR} ${PROCFLAGS} process_file "${INPUTDIR}/work.uk.xhtml" "${INPUTDIR}/default.xsl" "en" >"${OUTPUTDIR}/work.uk.html"
${OUTPUTDIR}/work.html.uk:
	ln -sf "work.uk.html" "${OUTPUTDIR}/work.html.uk"
all: ${OUTPUTDIR}/work.zh.html ${OUTPUTDIR}/work.html.zh
${OUTPUTDIR}/work.zh.html: ${INPUTDIR}/work.*.xhtml ${INPUTDIR}/default.xsl ${INPUTDIR}/tools/texts-en.xml ${INPUTDIR}/tools/texts-en.xml  ${INPUTDIR}/tools/menu-global.xml 
	${PROCESSOR} ${PROCFLAGS} process_file "${INPUTDIR}/work.zh.xhtml" "${INPUTDIR}/default.xsl" "en" >"${OUTPUTDIR}/work.zh.html"
${OUTPUTDIR}/work.html.zh:
	ln -sf "work.zh.html" "${OUTPUTDIR}/work.html.zh"

Full Makefile

Makerun

[02:09:09] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.ro.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.ro.html"
[02:09:26] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.ru.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.ru.html"
[02:09:26] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.sk.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.sk.html"
[02:09:42] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.sl.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.sl.html"
[02:09:42] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.sq.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.sq.html"
[02:09:58] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.sr.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.sr.html"
[02:09:58] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.sv.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.sv.html"
[02:10:15] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.tr.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.tr.html"
[02:10:15] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.uk.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.uk.html"
[02:10:32] "/srv/www/test.fsfe.org_git/build/process_file.sh" --source "/srv/www/test.fsfe.org_git" --statusdir "/srv/www/status.fsfe.org/test.fsfe.org" --domain "www.fsfe.org" process_file "/srv/www/test.fsfe.org_git/tags/tags.zh.xhtml" "/srv/www/test.fsfe.org_git/tags/tags.xsl" "en" >"/srv/www/test.fsfe.org_stage/tags/tags.zh.html"
view full

Errors

2017-08-31 00:43:57: Fatal - See buildlog for errors reported by Make
2017-08-31 09:30:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:31:03: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:32:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:33:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:34:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:35:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:36:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:37:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:38:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:39:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 09:40:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 11:28:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 11:29:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:08:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:09:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:10:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:13:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:14:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:15:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:16:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:17:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:18:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:19:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:20:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:21:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:22:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:23:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:24:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:25:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:26:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:27:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:28:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:29:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:30:01: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:31:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2017-08-31 12:32:02: Fatal - SVN reported the following problem:
 svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
svn: E200030: Additional errors:
svn: E200030: sqlite[S13]: database or disk is full
2018-02-20 22:58:02: Fatal - GIT reported the following problem:
 From https://git.fsfe.org/FSFE/fsfe-website
 + 04b87e0...c0662d2 test       -> origin/test  (forced update)
2018-02-20 22:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:04:26: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-02-20 23:09:01: Fatal - GIT reported the following problem:
 You have not concluded your merge (MERGE_HEAD exists).
Please, commit your changes before you can merge.
2018-02-20 23:34:17: Fatal - See buildlog for errors reported by Make
2018-02-26 14:57:20: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: No route to host
2018-02-26 14:58:04: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: No route to host
2018-02-26 14:59:05: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: No route to host
2018-02-26 15:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:03:05: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: No route to host
2018-02-26 15:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:05:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:06:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-02-26 15:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-09 22:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-09 22:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-27 15:19:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-27 15:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-31 02:19:17: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-03-31 02:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:42:17: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: Connection refused
2018-04-10 02:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:44:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:49:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-10 02:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-26 16:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-26 16:58:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-26 16:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:17:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:46:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:48:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-04-29 22:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:23:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:25:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:26:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-05-26 08:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-06-21 00:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-07-28 23:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:14:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:15:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:35:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:37:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:40:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-28 23:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:08:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:34:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:35:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:38:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:40:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:54:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:55:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:56:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 00:59:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:05:00: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:09:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:17:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 02:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:10:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:28:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:46:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:48:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 03:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:03:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:05:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:08:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:12:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:17:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:18:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:44:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:48:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 04:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:10:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:29:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 05:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:05:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:06:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:13:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:15:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:18:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:26:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 06:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:04:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:05:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:09:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:10:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:25:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:27:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:37:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:40:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:47:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 07:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:10:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:44:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:48:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 08:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:16:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 09:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:10:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:27:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:49:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 10:59:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:05:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:06:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:15:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:17:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:27:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:35:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:36:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:40:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:50:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:57:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 11:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:00:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:02:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:12:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:13:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:14:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:15:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:16:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:17:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:19:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:20:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:22:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:23:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:24:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:25:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:26:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:28:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:30:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:32:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:33:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:34:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:35:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:36:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:37:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:38:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:39:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:40:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:41:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:42:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:43:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:44:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:45:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:46:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:47:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:48:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:49:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:50:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:51:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:52:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:53:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:55:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:57:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:58:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 12:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 13:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-07-29 13:01:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2018-08-16 22:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:07:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 22:58:18: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: Connection refused
2018-08-16 22:59:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-16 23:00:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-27 13:29:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-08-29 18:02:18: Fatal - GIT reported the following problem:
 From https://git.fsfe.org/FSFE/fsfe-website
 + 8e1feed...82f4677 test       -> origin/test  (forced update)
2018-08-29 18:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:23:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:37:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:43:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 18:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:13:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:24:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:37:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:55:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:57:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 19:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:19:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:30:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:39:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:57:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 20:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:19:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:25:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:43:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:57:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 21:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:23:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:25:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:37:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 22:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-29 23:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 00:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:30:05: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 04:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 05:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 06:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:19:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 07:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:24:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 08:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:24:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 09:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:23:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 10:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 11:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:30:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:37:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 12:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:47:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 13:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:52:02: Fatal - GIT reported the following problem:
 
2018-08-30 14:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-08-30 14:55:01: Fatal - GIT reported the following problem:
 error: cannot open .git/FETCH_HEAD: Permission denied
2018-09-10 13:09:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-09-10 13:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-07 21:29:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-07 21:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-10 09:54:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-10 09:55:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-10 09:56:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:02:20: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': Failed to connect to git.fsfe.org port 443: No route to host
2018-10-19 22:03:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:04:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:05:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:06:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:07:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:08:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:09:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:10:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-10-19 22:11:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-04 10:52:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-06 06:14:01: Fatal - GIT reported the following problem:
 fatal: repository 'https://git.fsfe.org/FSFE/fsfe-website.git/' not found
2018-11-24 13:58:15: Fatal - GIT reported the following problem:
 From https://git.fsfe.org/FSFE/fsfe-website
 + c2cf142...f563186 test       -> origin/test  (forced update)
warning: Cannot merge binary files: graphics/jan.jpg (HEAD vs. f56318606840a0b01ccc9fc6a1ab7b33eaf16096)
2018-11-24 13:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:55:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 14:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:13:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:30:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 15:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:43:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 16:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:12:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:15:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:30:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 17:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:24:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:39:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 18:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:19:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 19:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:17:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:39:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:43:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 20:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:47:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:57:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 21:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:36:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 22:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:23:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-24 23:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:46:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 00:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:14:04: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:19:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:52:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 04:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:14:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:33:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:37:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:50:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 05:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:30:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:47:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 06:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:22:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:34:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:56:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 07:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:04:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:11:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 08:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:06:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:08:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:21:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:26:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:38:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:39:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 09:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:13:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:24:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:44:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 10:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:09:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:39:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:42:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:45:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:48:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:51:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:55:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 11:59:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:03:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:05:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:53:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 12:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:00:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:32:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:47:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:55:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 13:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:10:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:13:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:16:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:27:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:29:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:31:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:40:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:49:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:54:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:55:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:57:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:58:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 14:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:01:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:02:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:07:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:13:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:18:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:20:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:21:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:28:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:29:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:35:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:36:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:41:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:43:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:53:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:54:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:56:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:57:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:58:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 15:59:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:00:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:01:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:02:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:03:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:04:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:05:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:06:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:07:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:08:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:09:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:10:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:11:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:12:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:14:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:15:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:16:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:17:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:18:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:19:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:20:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:22:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:23:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:24:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:25:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:26:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:27:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:28:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:30:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:31:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:32:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:33:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:34:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:35:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:37:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:38:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:39:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:40:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:41:02: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:42:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:43:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:44:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:45:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:46:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:47:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:48:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:49:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:50:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:51:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-25 16:52:01: Fatal - GIT reported the following problem:
 Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
2018-11-27 09:30:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-27 09:31:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 14:18:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 14:19:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 14:20:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 14:21:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 17:28:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-11-29 17:29:02: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-12-10 15:45:01: Fatal - GIT reported the following problem:
 fatal: unable to access 'https://git.fsfe.org/FSFE/fsfe-website.git/': The requested URL returned error: 502
2018-12-15 20:27:06: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:30:03: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:31:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:39:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:43:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:49:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 20:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:14:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:21:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:24:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:27:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:36:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 21:59:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:01:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:16:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:18:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:22:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:34:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:39:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:50:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 22:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:02:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:14:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:18:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:24:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:32:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:35:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:37:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:42:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:43:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:51:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:53:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-15 23:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:13:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:24:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:27:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:36:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:43:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:49:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:53:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 00:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:17:05: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:18:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:19:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:39:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:42:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:49:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:51:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 02:59:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:02:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:06:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:08:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:18:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:19:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:22:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:24:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:35:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:39:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:50:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 03:59:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:01:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:06:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:08:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:14:04: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:15:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:19:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:21:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:35:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:43:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:44:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:53:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:56:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 04:59:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:02:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:06:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:13:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:14:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:21:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:32:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:43:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:48:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:56:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 05:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:02:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:19:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:22:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:27:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:32:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:36:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:56:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 06:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:06:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:09:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:16:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:24:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:34:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:36:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 07:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:08:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:13:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:34:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:37:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:42:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:44:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:48:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:50:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:54:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 08:59:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:09:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:13:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:32:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:34:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 09:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:01:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:06:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:08:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:11:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:12:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:16:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:19:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:21:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:26:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:29:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:31:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:33:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:35:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:37:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:48:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 10:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:01:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:03:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:07:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:09:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:25:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:27:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:31:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:36:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:39:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:42:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:48:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:51:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:52:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:53:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:54:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:56:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 11:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:04:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:05:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:10:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:16:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:17:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:18:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:20:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:21:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:23:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:27:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:28:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:29:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:30:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:31:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:35:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:37:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:38:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:40:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:41:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:42:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:45:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:46:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:47:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:48:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:51:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:53:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:55:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:56:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:57:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:58:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 12:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:00:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:01:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:02:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:03:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:04:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:05:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:06:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:07:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:08:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:09:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:10:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:11:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:12:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:13:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:14:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:15:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:16:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:17:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:18:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:19:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:20:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:21:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:22:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:23:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:24:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:25:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:26:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:27:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:28:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:30:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:31:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:32:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:33:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:34:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:35:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:36:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:37:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:38:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:39:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:40:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:41:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:42:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:43:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:44:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:45:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:46:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:47:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:48:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:49:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:50:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:51:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:52:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:53:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:54:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:55:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:56:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:57:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:58:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 13:59:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 14:00:02: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 14:01:01: Fatal - GIT reported the following problem:
 fatal: Unable to create '/srv/www/test.fsfe.org_git/.git/refs/remotes/origin/feature/newsletter-2018-12-de.lock': Permission denied
2018-12-16 14:02:02: Fatal - GIT reported the following problem:
 fatal: Unable to create &apo