From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brandon Casey Subject: Re: The 8th airing of the msysGit herald Date: Mon, 03 Mar 2008 12:48:14 -0600 Message-ID: <47CC47EE.9060004@nrlssc.navy.mil> References: <200803030210.02223.jnareb@gmail.com> <47CBE85B.6060702@imap.cc> <47CC419E.7030704@imap.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Johannes Schindelin , Jakub Narebski , git@vger.kernel.org To: Tilman Schmidt X-From: git-owner@vger.kernel.org Mon Mar 03 19:49:08 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1JWFij-0005Vy-Uz for gcvg-git-2@gmane.org; Mon, 03 Mar 2008 19:49:06 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752026AbYCCSs1 (ORCPT ); Mon, 3 Mar 2008 13:48:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751648AbYCCSs1 (ORCPT ); Mon, 3 Mar 2008 13:48:27 -0500 Received: from mail1.nrlssc.navy.mil ([128.160.35.1]:53231 "EHLO mail.nrlssc.navy.mil" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750960AbYCCSs0 (ORCPT ); Mon, 3 Mar 2008 13:48:26 -0500 Received: from starfish.gems.nrlssc.navy.mil (localhost [127.0.0.1]) by mail.nrlssc.navy.mil (8.13.7/8.13.7) with ESMTP id m23ImFED010553; Mon, 3 Mar 2008 12:48:16 -0600 Received: from tick.nrlssc.navy.mil ([128.160.25.48]) by starfish.gems.nrlssc.navy.mil with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Mar 2008 12:48:14 -0600 User-Agent: Thunderbird 2.0.0.9 (X11/20071031) In-Reply-To: <47CC419E.7030704@imap.cc> X-OriginalArrivalTime: 03 Mar 2008 18:48:14.0647 (UTC) FILETIME=[233AA470:01C87D5F] X-TM-AS-Product-Ver: : ISVW-6.0.0.2339-5.0.0.1023-15764001 X-TM-AS-Result: : Yes--11.021000-0-31-1 X-TM-AS-Category-Info: : 31:0.000000 X-TM-AS-MatchedID: : =?us-ascii?B?MTUwNTY3LTcwMTU3NS03MDAw?= =?us-ascii?B?NzUtMTM5MDEwLTE4ODAxOS03MDIxODktNzAyNDc0LTcxMDIwNi03?= =?us-ascii?B?MDIxOTItNzAzNzQ3LTcwMjA0NC03MDIzNTgtNzA1Mzg4LTcwNTQ1?= =?us-ascii?B?MC03MDQ0MjUtNzAxMjQ5LTcwNjc3MS03MDA2NDgtNzA4MDYwLTcw?= =?us-ascii?B?MTQ1NS03MDA3MjctNzAyNjM2LTcwMjgwNy03MDA4ODEtNzAxNzQ5?= =?us-ascii?B?LTcwODY1NS03MDA0NzAtNzA1NTAyLTcxMDI3Mi0xMTMyMTEtNzA3?= =?us-ascii?B?MTA0LTcwMDk3MS03MDcwNTYtNzAwNzU2LTcwMzM5OS03MDY1NjQt?= =?us-ascii?B?NzA5ODIzLTcwMzc4OC03MDAwNDAtNzAxMDUzLTcwMjAyMC03MDA2?= =?us-ascii?B?OTUtNzA5OTYwLTcwMjc2Mi03MDMyODMtMTQ4MDM5LTE0ODA1MS0y?= =?us-ascii?B?MDA0Mw==?= Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Tilman Schmidt wrote: > Am 03.03.2008 13:05 schrieb Johannes Schindelin: >> On Mon, 3 Mar 2008, Tilman Schmidt wrote: >> >>> Jakub Narebski schrieb: > [...] >>>> For me the sign how incredibly fast the git development is is the fact >>>> that git version from a year ago is considered "ancient". >>> Yes, and that is in itself a problem for people like me who just want to >>> use git to get some work done. The time I spend installing new git >>> versions, reading RelNotes and sorting through a rather high-volume >>> mailing list goes off the time I can spare for working on the Linux >>> driver I maintain. :-( >> Well, you do not _have_ to upgrade, if you are comfortable with what you >> have... > > True as far as it goes, and for appropriate values of "what I have". > Neither do I _have_ to subscribe to the mailing list, or, for that > matter, to read the release notes of a new version I install. > > But git is not particularly easy to learn on my own, so I end up > asking for help. (Arguably this qualifies as "not comfortable with > what I have.") And then "ancient version" translates all too easily > into "you should upgrade to a newer one". I think the assumption made was that you were already getting some work done with the version of git that you had. If you do not yet have a comfortable grasp of git usage I would suggest the following steps: 1) Grab "a" version of git (preferably latest stable version) -If you need to compile it, read the "INSTALL" file. 2) Read intro/tutorials -tutorial.txt -everyday.txt -user-manual.txt (more in-depth) These three are mentioned in the git man page. 3) Start using it -refer to man pages to answer questions as you encounter issues -ask the mailing list when man pages or other docs are unable to answer your questions 4) End of story Upgrading, reading RelNotes, using new features, and reading the high-volume mailing list are not required, so it is wrong to suggest that they are barriers to entry for using git. -brandon