git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* no --dry-run to git-pull ?
@ 2008-07-04 13:56 Neshama Parhoti
  2008-07-04 13:59 ` Miklos Vajna
  0 siblings, 1 reply; 4+ messages in thread
From: Neshama Parhoti @ 2008-07-04 13:56 UTC (permalink / raw)
  To: git

Hi,

Isn't there a way to do a --dry-run with git-pull ?

Thank you,
pnesh

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: no --dry-run to git-pull ?
  2008-07-04 13:56 no --dry-run to git-pull ? Neshama Parhoti
@ 2008-07-04 13:59 ` Miklos Vajna
  2008-07-04 15:26   ` Neshama Parhoti
  0 siblings, 1 reply; 4+ messages in thread
From: Miklos Vajna @ 2008-07-04 13:59 UTC (permalink / raw)
  To: Neshama Parhoti; +Cc: git

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: no --dry-run to git-pull ?
  2008-07-04 13:59 ` Miklos Vajna
@ 2008-07-04 15:26   ` Neshama Parhoti
  2008-07-04 15:29     ` Miklos Vajna
  0 siblings, 1 reply; 4+ messages in thread
From: Neshama Parhoti @ 2008-07-04 15:26 UTC (permalink / raw)
  To: Miklos Vajna; +Cc: git

On Fri, Jul 4, 2008 at 4:59 PM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> 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.

What puzzles me is the origin keyword. Is it set only if I initially
cloned a repo ?
Because in my case, I have just rsync'ed a repo to another station, so
I fear it will have no meaning in my case.
Thank you
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: no --dry-run to git-pull ?
  2008-07-04 15:26   ` Neshama Parhoti
@ 2008-07-04 15:29     ` Miklos Vajna
  0 siblings, 0 replies; 4+ messages in thread
From: Miklos Vajna @ 2008-07-04 15:29 UTC (permalink / raw)
  To: Neshama Parhoti; +Cc: git

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

On Fri, Jul 04, 2008 at 06:26:02PM +0300, Neshama Parhoti <pneshama@gmail.com> wrote:
> > 1) Replace origin and master with your remote 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.
> 
> What puzzles me is the origin keyword. Is it set only if I initially
> cloned a repo ?
> Because in my case, I have just rsync'ed a repo to another station, so
> I fear it will have no meaning in my case.

Heh. git remote add -f origin <url>, then you'll have it. And yes, you
have it if you cloned the repo, of course rsync won't add it. ;-)

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-07-04 15:30 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-04 13:56 no --dry-run to git-pull ? Neshama Parhoti
2008-07-04 13:59 ` Miklos Vajna
2008-07-04 15:26   ` Neshama Parhoti
2008-07-04 15:29     ` Miklos Vajna

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).