From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: Malformed branch name in fast-export when specifying non-HEAD/branch revision Date: Mon, 22 Aug 2011 12:19:32 -0400 Message-ID: <20110822161932.GA1945@sigill.intra.peff.net> References: <7vliurd62x.fsf@alter.siamese.dyndns.org> <20110817231922.GA28966@sigill.intra.peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Junio C Hamano , Elijah Newren , Owen Stephens , git@vger.kernel.org To: Sverre Rabbelier X-From: git-owner@vger.kernel.org Mon Aug 22 18:19:42 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QvXDx-0008TZ-Vh for gcvg-git-2@lo.gmane.org; Mon, 22 Aug 2011 18:19:42 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752940Ab1HVQTh (ORCPT ); Mon, 22 Aug 2011 12:19:37 -0400 Received: from 99-108-226-0.lightspeed.iplsin.sbcglobal.net ([99.108.226.0]:56870 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751537Ab1HVQTg (ORCPT ); Mon, 22 Aug 2011 12:19:36 -0400 Received: (qmail 17782 invoked by uid 107); 22 Aug 2011 16:20:17 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.84) with ESMTPA; Mon, 22 Aug 2011 12:20:17 -0400 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Mon, 22 Aug 2011 12:19:32 -0400 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Sun, Aug 21, 2011 at 03:29:38PM -0700, Sverre Rabbelier wrote: > > Yes, this was the conclusion I came to when I looked at this a month or > > so ago. You really need to give fast-export a mapping of objects to > > refnames, and it should output ref names _only_ for the mapping. That > > would handle this "not a ref" case, but would also let you push > > "refs/heads/foo" when it is equivalent to "refs/heads/master", without > > fast-export mentioning "refs/heads/master" at all. > > Does this bring any new insights into how the problem I was pointing > out (trying to push next if master points at the same commit does > nothing) could/should be solved? Hmm. Maybe I am misremembering the problem, but I thought that worked already. If you say: git fast-export refs/heads/foo you should get only reset/commit lines in the output for refs/heads/foo, no? Now I can't seem to replicate the case where refs/heads/master is mentioned, but you didn't want it to be. I may have to go back and re-read the thread from a month or two ago when we discussed these issues. -Peff