git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Geoffrey Irving" <irving@naml.us>
To: git@vger.kernel.org
Subject: git push won't push to a local branch
Date: Sun, 4 May 2008 11:49:38 -0700	[thread overview]
Message-ID: <7f9d599f0805041149w1955138crf269853196391e51@mail.gmail.com> (raw)

Hello,

There's an asymmetry between push and pull that seems unnecessary:
pull can pull from local branches, but push can't push to them.  Is
there a reason for this asymmetry?

In more detail, if I have a working copy with two branches, local and
master, I can use git pull to pull changes from master to local:

% git checkout local
% git pull . master
... pulls changes from master to local branch

If I make a change in local and try to do the reverse with git push,
it gives a confusing non-error message and doesn't do anything:

% git checkout local
% git rm scratch/pcomm.h
% git commit
% git push . master
Everything up-to-date

I can simulate the desired effect by switching to master and doing a pull.

% git checkout master
Switched to branch "master"
% git pull . local
Updating 0080774..7e8d678
Fast forward
 scratch/pcomm.h |  146 -------------------------------------------------------
 1 files changed, 0 insertions(+), 146 deletions(-)
 delete mode 100644 scratch/pcomm.h

I'd prefer not to have to switch my checkout to master to accomplish
this, since I'll end up with a corrupted working copy if I push from
somewhere else to master at the same time (I want to avoid multiple
repository copies to save space).

Thanks,
Geoffrey

             reply	other threads:[~2008-05-04 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 18:49 Geoffrey Irving [this message]
2008-05-04 19:19 ` git push won't push to a local branch Björn Steinbrink
2008-05-04 20:00   ` Geoffrey Irving

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=7f9d599f0805041149w1955138crf269853196391e51@mail.gmail.com \
    --to=irving@naml.us \
    --cc=git@vger.kernel.org \
    /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).