From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [1.8.0] Remote tag namespace Date: Tue, 1 Feb 2011 13:14:29 -0500 Message-ID: <20110201181428.GA6579@sigill.intra.peff.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Git Mailing List , Nicolas Pitre To: Nguyen Thai Ngoc Duy X-From: git-owner@vger.kernel.org Tue Feb 01 19:14:39 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 1PkKkQ-0003P3-3E for gcvg-git-2@lo.gmane.org; Tue, 01 Feb 2011 19:14:38 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755715Ab1BASOc (ORCPT ); Tue, 1 Feb 2011 13:14:32 -0500 Received: from xen6.gtisc.gatech.edu ([143.215.130.70]:45573 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755515Ab1BASOb (ORCPT ); Tue, 1 Feb 2011 13:14:31 -0500 Received: (qmail 21076 invoked by uid 111); 1 Feb 2011 18:14:30 -0000 Received: from 99-108-226-0.lightspeed.iplsin.sbcglobal.net (HELO sigill.intra.peff.net) (99.108.226.0) (smtp-auth username relayok, mechanism cram-md5) by peff.net (qpsmtpd/0.40) with ESMTPA; Tue, 01 Feb 2011 18:14:30 +0000 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Tue, 01 Feb 2011 13:14:29 -0500 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 Tue, Feb 01, 2011 at 05:44:50PM +0700, Nguyen Thai Ngoc Duy wrote: > OK I'm not familiar with tag code, but I can try. > > Proposal: > > Reserve refs/remote-tags namespace to store tags from remotes. Its > structure is the same as in refs/remotes. When pulling tags, put them > in refs/remote-tags/ instead of refs/tags. > Tag dereference code will be taught about refs/remote-tags with > similar deref order as in remote branches. There are similar questions around remote notes refs. Should there also be a refs/remote-notes? And there was some discussion recently about fetching remote replace refs. Should we perhaps be massaging refs/remotes into a structure to handle all of these things? Like: refs/remotes/origin/HEAD (-> refs/remotes/origin/heads/master) refs/remotes/origin/heads/master refs/remotes/origin/tags/v1.7.4 refs/remotes/origin/notes/commit refs/remotes/origin/replace/f67e92af477a2255b64a1ece33d9d126e763fe9b i.e., make refs/remotes/* an actual mirror of selected parts of the remote's refs/ hierarchy. And then figure out sane rules for merging those namespaces into the ref lookup procedure. For heads and tags, probably some tweaking of the lookup rules in dwim_ref; for replacements, probably you would want to manually say "I am interested in this replace" and copy or symref-link it into your refs/ hierarchy. And probably something similar with notes. Obviously I haven't thought it all the way through, but it just seems a shame not to deal with other similar issues when looking at tags. -Peff