public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox•net>
To: "Martin Langhoff" <martin.langhoff@gmail•com>
Cc: "Junio C Hamano" <junkio@cox•net>,
	"Git Mailing List" <git@vger•kernel.org>
Subject: Re: pull/push inconsistencies
Date: Tue, 15 May 2007 18:22:29 -0700	[thread overview]
Message-ID: <7v646th8a2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90705151811o2159aa5ai84a13e77e790e376@mail.gmail.com> (Martin Langhoff's message of "Wed, 16 May 2007 13:11:02 +1200")

"Martin Langhoff" <martin.langhoff@gmail•com> writes:

> There are 2 things that I see as wrong...
> - local .git/refs/remote/origin/foo and refs/heads/foo match - why is
> git-push talking about updating them?

Ooo...

Do you mean if you have refs/remotes/origin/foo locally, and
push into a repository that has refs/heads/foo (but not
refs/remotes/origin/foo), the push results in refs/heads/foo
getting updated?  If that is what is happening (without any
refspecs to instruct git-push to do so) that sounds quite buggy.
I need to look into the code for this one.

And I think earlier one I was confused that I thought you were
talking about pushing into refs/heads/branch (where branch is
checked out).  Sorry.

> - matching refs should ignore .git/refs/remote
>
> ... the 'matching refs' thing will
> ignore the local .git/refs/remotes directory. AFAICS it's the only
> sane thing to do.

I think you are probably right in that matching only heads and
perhaps tags is a sane thing to do (even tags/ is debatable, as
they are supposed to be immutable by convention).  As a matter
of fact I do not recall which part of refs/ namespace it looks
at, but it is a very old part of the system and I would not be
surprised if it silently assumed that there are only heads and
tags there (and not explicitly matching heads and tags only).

  reply	other threads:[~2007-05-16  1:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 22:53 pull/push inconsistencies Martin Langhoff
2007-05-15 23:21 ` Jakub Narebski
2007-05-16  0:24 ` Junio C Hamano
2007-05-16  1:11   ` Martin Langhoff
2007-05-16  1:22     ` Junio C Hamano [this message]
2007-05-16  1:40       ` J. Bruce Fields
2007-05-16  1:51         ` Martin Langhoff
2007-05-16  2:30           ` Junio C Hamano
2007-05-16 22:35           ` Martin Langhoff
2007-05-16 12:02   ` Jeff King
2007-05-16  2:50 ` [PATCH] " Daniel Barkalow

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=7v646th8a2.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=martin.langhoff@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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