From: Johannes Sixt <j.sixt@viscovery.net>
To: Christoph Duelli <duelli@melosgmbh.de>
Cc: git@vger.kernel.org
Subject: Re: Is a given file known to git?
Date: Tue, 11 Mar 2008 08:38:36 +0100 [thread overview]
Message-ID: <47D636FC.2060203@viscovery.net> (raw)
In-Reply-To: <47D6317D.7030700@melosgmbh.de>
Christoph Duelli schrieb:
> Given a repository and a path p to a file in it:
> Is it possible (how?) to detect (in a bash script) if the file pointed
> to by p is "known" to git?
> Something along the line:
> if `git knows p?
> then
> ...
> fi
For simplicity, I'll assume with "known to git" you mean whether the
current branch's tip has some content at the given path. Then you could write:
if git rev-parse HEAD:"$p" >/dev/null 2>&1
then
# git knows about $p
else
# git does not know about $p
fi
-- Hannes
next prev parent reply other threads:[~2008-03-11 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 7:15 Is a given file known to git? Christoph Duelli
2008-03-11 7:24 ` Shawn O. Pearce
2008-03-11 7:38 ` Johannes Sixt [this message]
2008-03-11 9:27 ` Christoph Duelli
2008-03-11 9:36 ` Johannes Sixt
2008-03-11 9:41 ` Christoph Duelli
2008-03-11 9:45 ` Junio C Hamano
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=47D636FC.2060203@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=duelli@melosgmbh.de \
--cc=git@vger.kernel.org \
/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).