All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Panayis <adam@movency.com>
To: Pieter de Bie <pieter@frim.nl>
Cc: git@vger.kernel.org
Subject: Re: Strange branch merging.
Date: Thu, 12 Feb 2009 12:40:04 +0000	[thread overview]
Message-ID: <499418A4.9060401@movency.com> (raw)
In-Reply-To: <E65A809A-65AD-4755-8AA7-32AA11C9AB5A@frim.nl>

Pieter, thanks for your advice.

I am never using the push command here.

Box A has branches master and blah.
On Box B I just want to pull branch master.

When I try to do that on box B I get the master branch from box A but I 
get the changes made to branch blah on box A.

I do not understand why, on box B, the master branch is showing changes 
made to the blah branch on box A. (Yet on box A the changes to the blah 
branch are not shown in the master)

Apologies for my babbling.

Adam

Pieter de Bie wrote:
>
> On Feb 12, 2009, at 11:52 AM, Adam Panayis wrote:
>
>> Once this is done I double check my branches and it shows I still 
>> only have the master. Perfect. However, when I check the file I 
>> edited on my local machine on the blah branch, the changes are there.
>>
>> Am I fundamentally misunderstanding the correct usage of git? Is this 
>> result expected?
>
> Yes, git pull will never change anything on the remote side. You 
> should use 'git push' for that. But, you shouldn't push to repository 
> with a working directory unless you know what you're doing -- read 
> http://git.or.cz/gitwiki/GitFaq#non-bare for that.
>
> - Pieter

  reply	other threads:[~2009-02-12 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 11:52 Strange branch merging Adam Panayis
2009-02-12 12:27 ` Pieter de Bie
2009-02-12 12:40   ` Adam Panayis [this message]
2009-02-12 12:42     ` Pieter de Bie
2009-02-12 12:59       ` Adam Panayis
2009-02-12 13:08 ` Sitaram Chamarty

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=499418A4.9060401@movency.com \
    --to=adam@movency.com \
    --cc=git@vger.kernel.org \
    --cc=pieter@frim.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.