From: "Shawn O. Pearce" <spearce@spearce.org>
To: Ivan Zorin <ivan.a.zorin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how to check remote git repo for updates without pull/fetch
Date: Fri, 19 Dec 2008 08:33:00 -0800 [thread overview]
Message-ID: <20081219163300.GT32487@spearce.org> (raw)
In-Reply-To: <494BC89F.9070107@gmail.com>
Ivan Zorin <ivan.a.zorin@gmail.com> wrote:
> Hello. I have not very hard question, but I don't know how to better do
> it - could you tell me, please, does exist some way to check remote git
> repository for updates without downloading any essential files? I
> suppose, that such command should just type something like: "already
> updated", if current working tree identical to remote repo, and
> something like "there is some updates in remote repo", if remote repo
> has some new commits and/or branches. Thanks.
There aren't any commands to do it.
What you could do is write a script based upon git ls-remote. A
really simple one might be:
#!/bin/sh
remote=$1
o=.git/remote_cache.$remote
n=$o.new$$
git ls-remote $remote >$n
if [ -f $o ]
then
if diff $o $n >/dev/null
then
echo "No changes"
else
mv $n $o
echo "Updates available"
else
mv $n $o
echo "New remote remembered..."
fi
A much more complex one would actually rewrite refs/heads/ to
the correct refs/remotes/ namespace on your local repository and
compare the remote ref values to the local refs/remotes values.
Patches for git fetch --pretend or something might be interesting.
Though I recall a thread about this before on the MLand saying there
was no point. Its not like you can see how big the download would
be until after its over.
--
Shawn.
next prev parent reply other threads:[~2008-12-19 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 16:15 how to check remote git repo for updates without pull/fetch Ivan Zorin
2008-12-19 16:33 ` Shawn O. Pearce [this message]
2008-12-19 16:39 ` Ivan Zorin
2008-12-20 17:32 ` James Cloos
2008-12-20 23:41 ` David Aguilar
2008-12-21 0:02 ` Boyd Stephen Smith Jr.
2008-12-21 9:53 ` James Cloos
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=20081219163300.GT32487@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=ivan.a.zorin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.