From: Miklos Vajna <vmiklos@frugalware.org>
To: Neshama Parhoti <pneshama@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: no --dry-run to git-pull ?
Date: Fri, 4 Jul 2008 15:59:44 +0200 [thread overview]
Message-ID: <20080704135944.GA4729@genesis.frugalware.org> (raw)
In-Reply-To: <912ec82a0807040656y1c48cba8m6f9981f6bb97b36a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Fri, Jul 04, 2008 at 04:56:27PM +0300, Neshama Parhoti <pneshama@gmail.com> wrote:
> Isn't there a way to do a --dry-run with git-pull ?
Not really. But you can do a 'git fetch origin', then a
'git log master..origin/master', and it'll tell you what changes will be
merged if you do a 'git merge origin/master'.
NOTES:
1) Replace origin and master with your repomte and branch.
2) If this sounds cryptic for you, then it might be an important info
that by default a pull is a fetch + a merge.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-04 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 13:56 no --dry-run to git-pull ? Neshama Parhoti
2008-07-04 13:59 ` Miklos Vajna [this message]
2008-07-04 15:26 ` Neshama Parhoti
2008-07-04 15:29 ` Miklos Vajna
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=20080704135944.GA4729@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=pneshama@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).