Hello,
Is this proper behaviour:
root# su <username> -c "git commit --quiet -a -m \"templates generation\";" # On branch master nothing to commit (working directory clean) root# echo $? 1
root# git --version git version 1.7.1
Hello,
Is this proper behaviour:
root# su <username> -c "git commit --quiet -a -m \"templates generation\";" # On branch master nothing to commit (working directory clean) root# echo $? 1
root# git --version git version 1.7.1
Re: git commit return code
On Mon, Aug 9, 2010 at 15:32, Tomasz Pajor <nikon@puffy.pl> wrote:
> Is this proper behaviour: > > root# su <username> -c "git commit --quiet -a -m \"templates generation\";" > # On branch master > nothing to commit (working directory clean) > root# echo $? > 1
Yes, you asked it to create a commit, but there's nothing to commit. Hence the failure to commit.
Re: git commit return code
Tomasz Pajor <nikon@puffy.pl> writes:
> Hello, > > Is this proper behaviour: > > root# su <username> -c "git commit --quiet -a -m \"templates generation\";" > # On branch master > nothing to commit (working directory clean) > root# echo $? > 1
The exit status doesn't seem documented in the manpage, but it's expected behavior that "git commit" refuses to create an empty commit, and it seems sensible to "exit(1)" in this case.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/