From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Forrest Subject: [ANN] Pro Git Reedited - a New Version of the Pro Git Book Date: Mon, 02 Dec 2013 20:29:43 -0800 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Tue Dec 03 05:30:33 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Vnhd3-0006GN-3E for gcvg-git-2@plane.gmane.org; Tue, 03 Dec 2013 05:30:33 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754048Ab3LCEa1 convert rfc822-to-quoted-printable (ORCPT ); Mon, 2 Dec 2013 23:30:27 -0500 Received: from plane.gmane.org ([80.91.229.3]:45549 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754045Ab3LCEaY (ORCPT ); Mon, 2 Dec 2013 23:30:24 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vnhcr-00068y-SK for git@vger.kernel.org; Tue, 03 Dec 2013 05:30:21 +0100 Received: from c-24-130-122-178.hsd1.ca.comcast.net ([24.130.122.178]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Dec 2013 05:30:21 +0100 Received: from nobozo by c-24-130-122-178.hsd1.ca.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Dec 2013 05:30:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-24-130-122-178.hsd1.ca.comcast.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: When I started learning Git, I spent a fair amount of time reading Pro Git. I found that it was a 2 steps forward, 1 step back experience. By this I mean I=92d learn a couple of new things but then I=92d either read something I didn=92t understand, or else I=92d realize that my previous understanding was wrong. But, once I developed a better understanding of Git, I went back to re-read the sections that I didn=92t previously understand. I=92d almost always think to myself that if only this word or that phrase could be changed slightly, the concept would have been much easier to understand. This happens to me a lot when reading technical books. Given that Scott was generous enough to release Pro Git as a free book with the manuscript sources available at GitHub, I decided to return the favor by doing a complete edit in an attempt to improve the areas I had trouble with and to generally tighten up the text. I=92ve fed all these changes back to the maintainer of Pro Git via GitHub pull requests. He=92s free to decide what he wants to do with them. Meanwhile, I've published my own version of this book, which I call Pro Git Reedited. The PDF version of Pro Git Reedited is at https://www.dropbox.com/s/4awq55350ef235m/progitreedited.en.pdf and the source code is at https://github.com/nobozo/progitreedited I welcome your feedback. Please send any comments to me at nobozo@gmail.com. To make sure I recognize them as comments about this book, please include [PGR] in the subject. Jon Forrest nobozo@gmail.com