git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to figure out what 'git push' would do?
Date: Sun, 5 Aug 2007 19:33:40 +0200	[thread overview]
Message-ID: <20070805173340.GA3159@steel.home> (raw)
In-Reply-To: <267CDD46-549B-4BFE-B993-80CD1CFE75D8@zib.de>

Steffen Prohaska, Sun, Aug 05, 2007 13:37:34 +0200:
> How can I check what a 'git push' would do, without
> actually doing it?
> 
> Is there something like 'git push --dry-run', similar
> to 'rsync --dry-run'?

No. It is often safe to just do git-push, unless you have naive
developers doing pull every time some ref in your shared repo changes
*and* expecting the result to compile (typical for CVS way of work).
git-push will not overwrite anything, it always only forwards history.

For the case you really want to know what the changes on remote repo
will be it is possible to fetch them into the local repo first and
compare with what you will push:

    $ git fetch git://remote/path/REPO master:refs/remotes/REPO/master
    $ gitk local..REPO/master

It gives you all possible information, which may be worth that bit of
work. Or, if you have all the remote configuration ready, it can be
just:

    $ git fetch
    $ gitk local..REPO/master

  parent reply	other threads:[~2007-08-05 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 11:37 How to figure out what 'git push' would do? Steffen Prohaska
2007-08-05 11:42 ` David Kastrup
2007-08-05 17:33 ` Alex Riesen [this message]
2007-08-05 17:45   ` Julian Phillips
2007-08-05 19:56   ` Steffen Prohaska
2007-08-05 22:09     ` Alex Riesen

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=20070805173340.GA3159@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=prohaska@zib.de \
    /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).