cg-commit doesn't like new repository

cg-commit doesn't like new repository

[Alan Chandler]

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>] <tree-ish> 
[<path>...]
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<n>         limit rename attempts up to <n> paths.
  -O<file>      reorder diffs according to the <file>.
  -S<string>    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.

Re: cg-commit doesn't like new repository

[Petr Baudis]

Dear diary, on Sat, Nov 19, 2005 at 11:43:10PM CET, I got a letter
where Alan Chandler <alan@chandlerfamily.org.uk> said that...
> 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

cg-init -I ? Its help message would also explain to you how to make the
initial commit manually. ;-)

> I presume there is something that cg-init-db does which makes it suitable for 
> cogito - but what

cg-commit will try to determine the list of files to commit by diffing
against the previous commit, but there is no previous commit. You need
to pass cg-commit the -C option in order to make the initial commit.

> and shouldn't cg-commit notice and either do it automatically or give
> a different error message?

Good point. cg-commit will now print out friendly error message and
suggest you to use -C.

Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.