From: Josef Wolf <jw@raven.inka.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Problems using perl's Git.pm module
Date: Fri, 3 Dec 2010 09:14:14 +0100 [thread overview]
Message-ID: <20101203081414.GB26070@raven.wolf.lan> (raw)
In-Reply-To: <7vipzcrrk9.fsf@alter.siamese.dyndns.org>
On Thu, Dec 02, 2010 at 09:51:50AM -0800, Junio C Hamano wrote:
> Josef Wolf <jw@raven.inka.de> 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".
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!
prev parent reply other threads:[~2010-12-03 8:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 11:40 Problems using perl's Git.pm module Josef Wolf
2010-12-02 13:23 ` Ævar Arnfjörð Bjarmason
2010-12-02 16:19 ` Jonathan Nieder
2010-12-02 17:30 ` Ævar Arnfjörð Bjarmason
2010-12-02 17:46 ` Junio C Hamano
2010-12-02 18:10 ` demerphq
2010-12-02 18:14 ` Jonathan Nieder
2010-12-02 18:41 ` demerphq
2010-12-02 19:05 ` [RFC/PATCH] Git.pm: discourage casual use Jonathan Nieder
2010-12-02 19:30 ` Junio C Hamano
2010-12-02 19:45 ` Jonathan Nieder
2010-12-03 8:38 ` Problems using perl's Git.pm module Josef Wolf
2010-12-03 9:02 ` demerphq
2010-12-02 18:18 ` Junio C Hamano
2010-12-02 18:32 ` demerphq
2010-12-03 8:27 ` Josef Wolf
2010-12-03 9:10 ` Jonathan Nieder
2010-12-02 17:51 ` Junio C Hamano
2010-12-03 8:14 ` Josef Wolf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101203081414.GB26070@raven.wolf.lan \
--to=jw@raven.inka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).