From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl Worth Subject: Re: Difficulties in advertising a new branch to git newbies Date: Wed, 31 Jan 2007 11:50:13 -0800 Message-ID: <871wlbascq.wl%cworth@cworth.org> References: <87odognuhl.wl%cworth@cworth.org> <8aa486160701311127v686929c8vb9b5771031776ed8@mail.gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Wed_Jan_31_11:50:13_2007-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org To: "=?ISO-8859-1?Q?Santi_B=E9jar?=" X-From: git-owner@vger.kernel.org Wed Jan 31 20:52:20 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1HCLUB-0004u2-Sl for gcvg-git@gmane.org; Wed, 31 Jan 2007 20:51:16 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751556AbXAaTvM (ORCPT ); Wed, 31 Jan 2007 14:51:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751529AbXAaTvM (ORCPT ); Wed, 31 Jan 2007 14:51:12 -0500 Received: from cworth.org ([217.160.249.188]:48119 "EHLO theworths.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751457AbXAaTvM (ORCPT ); Wed, 31 Jan 2007 14:51:12 -0500 Received: (qmail 16203 invoked from network); 31 Jan 2007 14:50:14 -0500 Received: from localhost (HELO raht.cworth.org) (127.0.0.1) by localhost with SMTP; 31 Jan 2007 14:50:14 -0500 In-Reply-To: <8aa486160701311127v686929c8vb9b5771031776ed8@mail.gmail.com> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.4 Mule/5.0 (SAKAKI) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: --pgp-sign-Multipart_Wed_Jan_31_11:50:13_2007-1 Content-Type: text/plain; charset=US-ASCII On Wed, 31 Jan 2007 20:27:52 +0100, "=?ISO-8859-1?Q?Santi_B=E9jar?=" wrote: > Actually it is the same "problem" as when you want to work on the > non-HEAD remote branch. Yes, exactly. > It would be nice if: > > git clone -b ${branch} git://... > > would be equivalent of the above three commands. Yes, something like that would be extremely helpful! In addition, it would be great to have a command that did the same setup within an existing repository. And I would be most happy if the two commands for these two use cases shared as much syntax as possible, so I could publish one string and users could cut-and-paste it to either command as appropriate. One string I would have liked would have been "git://... ${branch}", but existing git-clone and git-fetch command syntax is not too amenable for that, (git-clone interprets an argument after the URL as the name of the local directory to create while git-fetch interprets the argument after the URL as a refspec). -Carl --pgp-sign-Multipart_Wed_Jan_31_11:50:13_2007-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFwPL16JDdNq8qSWgRAmjsAJ91n1vs1Oi0WdJKAKna76VmhWgZCACgpkqa oAGUW2Kvr9Bl9xgmCIjKHzo= =F8Y1 -----END PGP SIGNATURE----- --pgp-sign-Multipart_Wed_Jan_31_11:50:13_2007-1--