From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Leo Razoumov <slonik.az@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: How to check new commit availability without full fetch?
Date: Sun, 10 Jan 2010 12:38:07 -0800 [thread overview]
Message-ID: <7v8wc5itlc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1001101501520.10143@xanadu.home> (Nicolas Pitre's message of "Sun\, 10 Jan 2010 15\:13\:49 -0500 \(EST\)")
Nicolas Pitre <nico@fluxnic.net> writes:
>> I am sure I am not the only one with such an itch.
>
> Maybe you are. There is very little point knowing that the remote repo
> has new commits if you're not going to fetch them, so I don't understand
> why you need this.
A feel good factor is in play? IOW, "I am short of time, so I won't be
able to really afford to 'git pull' and test the result of re-integrating
my changes to what happened on the other end. If I can learn that there
is nothing happening over there, then I won't have to do anything and know
that I am up to date."
next prev parent reply other threads:[~2010-01-10 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 11:12 How to check new commit availability without full fetch? Leo Razoumov
2010-01-10 20:13 ` Nicolas Pitre
2010-01-10 20:38 ` Junio C Hamano [this message]
2010-01-10 21:05 ` Nicolas Pitre
2010-01-11 1:36 ` Leo Razoumov
2010-01-11 1:57 ` Tay Ray Chuan
2010-01-11 2:08 ` Junio C Hamano
2010-01-11 5:29 ` Michael Witten
2010-01-11 7:12 ` Junio C Hamano
2010-01-11 2:01 ` Nicolas Pitre
2010-01-11 16:22 ` Leo Razoumov
2010-01-11 17:04 ` Nicolas Pitre
2010-01-11 17:35 ` Leo Razoumov
2010-01-11 5:38 ` Dmitry Potapov
2010-01-11 7:31 ` Robin Rosenberg
2010-01-11 8:09 ` Junio C Hamano
2010-01-11 17:59 ` Nicolas Pitre
2010-01-11 19:20 ` Junio C Hamano
2010-01-11 20:52 ` Nicolas Pitre
2010-01-11 20:06 ` Andreas Schwab
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=7v8wc5itlc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=slonik.az@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 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).