From: Linus Torvalds <torvalds@linux-foundation.org>
To: Marc Haber <mh+git@zugschlus.de>
Cc: git@vger.kernel.org
Subject: Re: How to check repository/working tree status from a script
Date: Tue, 19 May 2009 09:18:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905190915050.3301@localhost.localdomain> (raw)
In-Reply-To: <20090519160031.GB23505@torres.zugschlus.de>
On Tue, 19 May 2009, Marc Haber wrote:
>
> On Tue, May 19, 2009 at 04:34:47PM +0100, Tony Finch wrote:
> > On Tue, 19 May 2009, Marc Haber wrote:
> > > I would like to check in a script whether there (a) are uncommitted
> > > changes (as in "working tree differs from local repository")
> >
> > # check working tree is not different from the index
> > git diff --quiet
> > # check that the index is not different from the head
> > git diff --quiet --cached
>
> $ git diff --quiet; echo $?
> 0
> $ git diff --quiet --cached; echo $?
> 0
> $ touch keks
> $ git diff --quiet; echo $?
> 0
> $ git diff --quiet --cached; echo $?
> 0
> $
>
> Am I missing something?
If "keks" is already something you know about, then 'touch' wouldn't have
changed it, so diff won't show it.
And if what you want to know about is whether there are _new_ files you
might want to check, then you need a third check: 'git ls-files'. You
won't see it in the error code, but you can do
others=$(git ls-files -o --exclude-standard)
and then check it 'others' is empty or not.
Linus
next prev parent reply other threads:[~2009-05-19 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 14:35 How to check repository/working tree status from a script Marc Haber
2009-05-19 15:34 ` Tony Finch
2009-05-19 16:00 ` Marc Haber
2009-05-19 16:16 ` Tony Finch
2009-05-20 14:28 ` Marc Haber
2009-05-19 16:18 ` Linus Torvalds [this message]
2009-05-19 16:29 ` Linus Torvalds
2009-05-20 14:27 ` Marc Haber
2009-05-20 11:10 ` Marc Haber
2009-05-20 11:19 ` Santi Béjar
2009-05-20 11:32 ` Johannes Sixt
2009-05-20 14:29 ` Marc Haber
2009-05-21 13:24 ` Marc Haber
2009-05-21 15:37 ` Jeff King
2009-05-23 20:39 ` Marc Haber
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=alpine.LFD.2.01.0905190915050.3301@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=mh+git@zugschlus.de \
/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).