From: Alan Chandler Date: Sat, 19 Nov 2005 22:43:10 GMT Subject: cg-commit doesn't like new repository Message-ID: <200511192243.10815.alan@chandlerfamily.org.uk> I just decided to make a repository of /etc, but because I didn't want to load in all the files, I used git-init-db to create the repository rather than cg-init-db I then did cg-add for fstab followed up by cg-commit which then failed as shown below As soon as I have done a git-commit, all is OK, and cg-commit works again. I presume there is something that cg-init-db does which makes it suitable for cogito - but what, and shouldn't cg-commit notice and either do it automatically or give a different error message? cg-commit usage: git-diff-index [-m] [--cached] [] [...] common diff options: -z output diff-raw with lines terminated with NUL. -p output patch format. -u synonym for -p. --name-only show only names of changed files. --name-status show names and status of changed files. -R swap input file pairs. -B detect complete rewrites. -M detect renames. -C detect copies. --find-copies-harder try unchanged files as candidate for copy detection. -l limit rename attempts up to paths. -O reorder diffs according to the . -S find filepair whose only one side contains the string. --pickaxe-all show all files diff when -S is used and hit is found. cg-commit: Nothing to commit root@kanger etc[master]# -- Alan Chandler http://www.chandlerfamily.org.uk Open Source. It's the difference between trust and antitrust.