git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: recent change in git.git/master broke my repos
Date: Thu, 25 Oct 2007 12:01:59 -0400	[thread overview]
Message-ID: <20071025160159.GA21505@coredump.intra.peff.net> (raw)
In-Reply-To: <86bqan6v9f.fsf@blue.stonehenge.com>

On Thu, Oct 25, 2007 at 08:58:52AM -0700, Randal L. Schwartz wrote:

> Jeff> So that should take the remote's refs/heads/* and put them in your
> Jeff> refs/remotes/origin/*. I don't see how that would have anything to do
> Jeff> with your 'refs/heads/upstream' branch.
> 
> Agreed, but that's the place where fetch might look at refs/heads/upstream,
> and the behavior is definitely different between yesterday and today.

Fair enough. How about my other questions. Can you 'git-show upstream'?
Can you 'git-show origin/master'?

-Peff

  reply	other threads:[~2007-10-25 16:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 14:32 recent change in git.git/master broke my repos Randal L. Schwartz
2007-10-25 15:01 ` Karl Hasselström
2007-10-25 17:46   ` Nicolas Pitre
2007-10-25 18:29     ` Randal L. Schwartz
2007-10-25 20:23     ` Andreas Ericsson
2007-10-25 20:38       ` Nicolas Pitre
2007-10-25 20:42         ` Andreas Ericsson
2007-10-26  7:39     ` Karl Hasselström
2007-10-25 15:51 ` Jeff King
2007-10-25 15:55   ` Randal L. Schwartz
2007-10-25 15:57     ` Jeff King
2007-10-25 15:58       ` Randal L. Schwartz
2007-10-25 16:01         ` Jeff King [this message]
2007-10-25 16:06           ` Randal L. Schwartz
2007-10-25 16:56 ` Jeff King
2007-10-25 18:05   ` Daniel Barkalow
2007-10-27  6:09     ` Junio C Hamano
2007-10-27 20:06       ` 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=20071025160159.GA21505@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.com \
    /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).