strange cg-add problem

Hello!

I try to backup a MySQLDump and put it into git so we have easy access
to diffs and can have a real history.

The problem I have is that it works perfectly, when running manually,
but when running in the script git refuses to use the file:

----------------------------------------------------------------------
srwali01:/home/server/backup/db# ~/db-dump.sh 
/home/server/backup/db//2005-11-22/13:26 does not exist or is not a regular file
cg-add: warning: not all files could be added
cg-commit: Nothing to commit
----------------------------------------------------------------------
(The script can be found at [0].)

When I do that on the command line, this happens:

----------------------------------------------------------------------
srwali01:/home/server/backup/db# cg-add /home/server/backup/db//2005-11-22/13:26
Adding file /home/server/backup/db//2005-11-22/13:26
Ignoring path /home/server/backup/db//2005-11-22/13:26
srwali01:/home/server/backup/db# cg-commit -m "Backup vom 2005-11-22 um 13:26"
cg-commit: Nothing to commit
----------------------------------------------------------------------

When I add it with a relative path it works:
----------------------------------------------------------------------
Adding file 2005-11-22/13:26
srwali01:/home/server/backup/db# cg-commit -m "Backup vom 2005-11-22 um 13:26"
A 2005-11-22/13:26
Committed as 3086174c1c84ce598137062867c07a4b7c619c39.
----------------------------------------------------------------------

When I change it in the script to be relativeo
[( cd "$DDIR"; cg-add "$SUBDIR/$FILENAME"; cg-commit -m "Backup vom $SUBDIR um $FILENAME") ]
than the same happens:

----------------------------------------------------------------------
srwali01:~# ./db-dump.sh 
2005-11-22/13:31 does not exist or is not a regular file
cg-add: warning: not all files could be added
cg-commit: Nothing to commit
----------------------------------------------------------------------

Any hint why it behaves differently in script and command line?

Btw, does someone know, why mysqldump does just one insert and a very very long line
and not many inserts with only one value? The bevahiour of it seems to have changed,
as mysqldump did that in earlier releases [sorry bit offtopic].

Greetings,

Nico


[0]: http://linux.schottelius.org/scripts/#db-dump+git.sh

-- 
Latest project: cinit-0.2.1 (http://linux.schottelius.org/cinit/)
Open Source nutures open minds and free, creative developers.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html