I agree with Yac that this error is unwarranted, though it's been like that since forever. If a repo is empty, git rev-list should probably just return without erroring out. The fix is trivial, if the list agrees that this is in fact legit. Atousa On Wed, Nov 11, 2015 at 10:26 AM, yac <yac@xxxxxxxxxxx> wrote: > Hello > > basics: > > % rpm -q git git-core > git-2.6.2-2.1.x86_64 > git-core-2.6.2-2.1.x86_64 > > ~ % grep PRETTY_NAME /etc/os-release > PRETTY_NAME="openSUSE Tumbleweed (20151030) (x86_64)" > > current behavior: > > ~ % git init no-commits > Initialized empty Git repository in /home/tester/no-commits/.git/ > ~ % git -C no-commits rev-list --all > usage: git rev-list [OPTION] <commit-id>... [ -- paths... ] > limiting output: > --max-count=<n> > --max-age=<epoch> > --min-age=<epoch> > --sparse > --no-merges > --min-parents=<n> > --no-min-parents > --max-parents=<n> > --no-max-parents > --remove-empty > --all > --branches > --tags > --remotes > --stdin > --quiet > ordering output: > --topo-order > --date-order > --reverse > formatting output: > --parents > --children > --objects | --objects-edge > --unpacked > --header | --pretty > --abbrev=<n> | --no-abbrev > --abbrev-commit > --left-right > --count > special purpose: > --bisect > --bisect-vars > --bisect-all > ~ % echo $? > 129 > > expected behavior: > > ~ % git -C no-commits rev-list --all > ~ % echo $? > 0 > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html