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 08:06:52 -0800 Message-ID: <87k5z3npsz.wl%cworth@cworth.org> References: <87odognuhl.wl%cworth@cworth.org> <8b65902a0701310513s1f8bfa04o7e1c7e43b7453ac8@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_08:06:47_2007-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org To: "Guilhem Bonnefille" X-From: git-owner@vger.kernel.org Wed Jan 31 17:12:02 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 1HCHzA-0005dB-J6 for gcvg-git@gmane.org; Wed, 31 Jan 2007 17:07:00 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030218AbXAaQG5 (ORCPT ); Wed, 31 Jan 2007 11:06:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030219AbXAaQG5 (ORCPT ); Wed, 31 Jan 2007 11:06:57 -0500 Received: from cworth.org ([217.160.249.188]:46549 "EHLO theworths.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1030218AbXAaQG5 (ORCPT ); Wed, 31 Jan 2007 11:06:57 -0500 Received: (qmail 19935 invoked from network); 31 Jan 2007 11:06:53 -0500 Received: from localhost (HELO raht.cworth.org) (127.0.0.1) by localhost with SMTP; 31 Jan 2007 11:06:53 -0500 In-Reply-To: <8b65902a0701310513s1f8bfa04o7e1c7e43b7453ac8@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_08:06:47_2007-1 Content-Type: text/plain; charset=US-ASCII On Wed, 31 Jan 2007 14:13:42 +0100, "Guilhem Bonnefille" wrote: > If the user is not a developer and only interested in testing, what > about a simple snapshot tarball? > So, you prepare the fix and then you pack everything in a > myapp-timestamp.tar.gz and send this tarball to the user. That's bad for all the same reasons we don't send tarballs around to each other. But here are several concrete points: 1. I want to be able to easily publicize a new branch with instructions that anyone can use, (regardless of git experience). 2. I've got the stuff available in a git branch already, and I don't want to do any more work. 3. I want the exchange to be as efficient as possible, (I might send multiple fixes in series to the user and it'd be really nice to take advantage of git's efficiency here). 4. I don't want to condemn the user to never being able to learn git. If I make this easy for the user then I get a nice lead-in to teach the user new things, (which is good for me since it helps me if the user starts sending me git commits rather than random patches without commit messages connected to who-knows-what tar-file version of the software, etc.) etc. etc. -Carl PS. All that being said, our project does publish periodic tar-file snapshots. But that's really for a different situation: specifically, for people with whom I'm not already engaged in any conversation at all. --pgp-sign-Multipart_Wed_Jan_31_08:06:47_2007-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD4DBQBFwL6c6JDdNq8qSWgRAjilAJ99LZybHXzd8ZGLv2BQpeOfWS1gxACYqQSk PxMT9ZfNXED2B70rEB9vWw== =hnsL -----END PGP SIGNATURE----- --pgp-sign-Multipart_Wed_Jan_31_08:06:47_2007-1--