Re: Problems using perl's Git.pm module

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Problems using perl's Git.pm module

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:50:09

Josef Wolf [off-list ref] writes:
  jw@raven:~/testrepos> git st
  # On branch master
  nothing to commit (working directory clean)
I take it that you have "alias.st.cmd = status".

Observe what this gives you:

    $ git st; echo $?

If you are running pre-1.7.0 version of git, I think "git status" was a
synonym to "git commit --dry-run" and exited with non-zero status to
signal the caller that there is nothing to commit, which is...
  jw@raven:~/testrepos> ./test.pl
  # On branch master
  nothing to commit (working directory clean)
  status failed w/ code 1 at ./test.pl line 9
...consistent with what we see here.

Re: Problems using perl's Git.pm module

From: Josef Wolf <hidden>
Date: 2016-06-15 22:50:09

On Thu, Dec 02, 2010 at 09:51:50AM -0800, Junio C Hamano wrote:
Josef Wolf [off-list ref] writes:
quoted
  jw@raven:~/testrepos> git st
  # On branch master
  nothing to commit (working directory clean)
I take it that you have "alias.st.cmd = status".
Yes, I'm still strongly tied to svn ;-)
Observe what this gives you:

    $ git st; echo $?
1
If you are running pre-1.7.0 version of git, I think "git status" was a
synonym to "git commit --dry-run" and exited with non-zero status to
signal the caller that there is nothing to commit, which is...
It's 1.6.4.2, so I guess you're right.

Thanks!
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help