From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl Worth Subject: Re: Making git disappear when talking about my code (was: Re: GIT vs Other: Need argument) Date: Wed, 25 Apr 2007 12:03:15 -0700 Message-ID: <878xcg6zv0.wl%cworth@cworth.org> References: <8b65902a0704170841q64fe0828mdefe78963394a616@mail.gmail.com> <200704171818.28256.andyparkins@gmail.com> <20070417173007.GV2229@spearce.org> <462521C7.2050103@softax.com.pl> <4627ABBB.8060709@softax.com.pl> <877is29b1l.wl%cworth@cworth.org> <7vps5ud91x.fsf@assigned-by-dhcp.cox.net> <87vefm7l6g.wl%cworth@cworth.org> <7v1wiabbfr.fsf@assigned-by-dhcp.cox.net> <87mz0w7g3j.wl%cworth@cworth.org> <87k5w07dft.wl%cworth@cworth.org> <87fy6o770w.wl%cworth@cworth.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Wed_Apr_25_12:03:15_2007-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Junio C Hamano , Marcin Kasperski , git@vger.kernel.org To: Nicolas Pitre X-From: git-owner@vger.kernel.org Wed Apr 25 21:03:55 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 1HgmmO-0006Qn-Dx for gcvg-git@gmane.org; Wed, 25 Apr 2007 21:03:52 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2992945AbXDYTDX (ORCPT ); Wed, 25 Apr 2007 15:03:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S2992948AbXDYTDX (ORCPT ); Wed, 25 Apr 2007 15:03:23 -0400 Received: from theworths.org ([217.160.253.102]:50631 "EHLO theworths.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2992947AbXDYTDW (ORCPT ); Wed, 25 Apr 2007 15:03:22 -0400 Received: (qmail 10065 invoked from network); 25 Apr 2007 15:03:16 -0400 Received: from localhost (HELO raht.cworth.org) (127.0.0.1) by localhost with SMTP; 25 Apr 2007 15:03:16 -0400 In-Reply-To: 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_Apr_25_12:03:15_2007-1 Content-Type: text/plain; charset=US-ASCII On Wed, 25 Apr 2007 14:07:23 -0400 (EDT), Nicolas Pitre wrote: > With all the safeties (reflogs, etc) this warning could be toned down > even more now. That would definitely help. > To me it looks like Git would perform some hardcoded magic without > helping the user understanding what is going on. That's a fine argument. > If you really want people to get at your code with no Git consideration > what so ever, then just direct them at the corresponding gitweb and/or > git-archive invocations with --remote= to store a local copy. But that's just it. It's not that I want people to get at my code with no git consideration. I believe that git provides the best way to get at my code, (since it allows not just getting at a single snapshot like git-archive would), but it allows for getting at everything in the past as well, and easily getting at stuff in the future. It's more that I want a single way to talk about some branch I've just published, (necessarily both a url and a branch), and I assume an audience with a wide range of git experience, (from none to lots). So I'm just looking for a simple way to advertise the branch that will work for the whole audience, (gitweb and git-archive aren't going to be much use for the experienced git user---except in an indirect way where the user could manually extract the useful parts of the instructions out of the noise). > And why again isn't detached head just fine for your usage scenario > instead? Only the "obnoxious" warning? No ability to easily follow the branch as new stuff comes along. Compare what one used to be able to do with pre-separate-remotes git: git clone git://git.kernel.org/pub/scm/git/git.git git checkout next git pull # occasionally to what you have now: git clone git://git.kernel.org/pub/scm/git/git.git git checkout origin/next And what's step 3 to follow this branch? Certainly, doing "git fetch" occasionally brings in the data, but there's no simple way to use detached head to just "follow along". So then the user has to learn new concepts like creating a tracking branch: git branch --track next origin/next git checkout next git pull # occasionally You can say that's just a series of simple commands, but it's still more concepts and commands than other systems, (including past versions of git). And for the user that's really just doing read-only branch tracking, I don't see where there's much benefit coming from the extra concepts and commands. -Carl --pgp-sign-Multipart_Wed_Apr_25_12:03:15_2007-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGL6Xz6JDdNq8qSWgRAnFBAKCSqR52Wh/REbfuD8i5OIj40yHTuwCfeZZp Cf2vuOKheBhZubXWtauoThI= =Tjvv -----END PGP SIGNATURE----- --pgp-sign-Multipart_Wed_Apr_25_12:03:15_2007-1--