From: Dmitry Potapov <dpotapov@gmail.com>
To: Leo Razoumov <slonik.az@gmail.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: How to check new commit availability without full fetch?
Date: Mon, 11 Jan 2010 08:38:15 +0300 [thread overview]
Message-ID: <20100111053815.GB10586@dpotapov.dyndns.org> (raw)
In-Reply-To: <ee2a733e1001101736p2f395de6ka05044fe7cca624d@mail.gmail.com>
On Sun, Jan 10, 2010 at 08:36:44PM -0500, Leo Razoumov wrote:
>
> BTW, pull and push are in a way symmetric operations.
Not really... 'pull' = 'fetch' + 'merge', while 'push' only propagates
changes without any merging. You can say 'fetch' and 'push' are in a way
symmetric operations, but this symmetry is limited due to difference in
usage between local and remote branches.
> Is there any
> deep reason why push supports --dry-run but pull/fetch does not??
I guess it is because no one needs it. 'push' has --dry-run, because
it updates local references in a remote repository. So, you may want
to be sure that you are pushing the right thing. On the other hand,
I see no reason to have --dry-run for 'fetch', because it updates only
remote references, making them to point to the current state of the
corresponding branches. 'fetch' does not change any local branch, so
I see no reason for --dry-run.
What use case do you have in mind that needs --dry-run for 'fetch'?
Dmitry
next prev parent reply other threads:[~2010-01-11 5: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
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 [this message]
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=20100111053815.GB10586@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).