From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: git on Cygwin: Not a valid object name HEAD Date: Mon, 13 Aug 2007 11:50:39 +0100 (BST) Message-ID: References: <30e4a070708080650j5de7ee92p4acd7e82de7d9dff@mail.gmail.com> <30e4a070708080941j49b3d58cxc39bbe65f2fee9d5@mail.gmail.com> <75EB313E-807D-44FB-A186-A151F182B47B@zib.de> <76795DDC-29A5-4C7E-B56E-A6316A183C75@zib.de> <2383328F-300E-459C-A299-90242DA230F7@zib.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Torgil Svensson , Git Mailing List , "Shawn O. Pearce" To: Steffen Prohaska X-From: git-owner@vger.kernel.org Mon Aug 13 12:51:57 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 1IKXWf-00055O-FP for gcvg-git@gmane.org; Mon, 13 Aug 2007 12:51:57 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941864AbXHMKvl (ORCPT ); Mon, 13 Aug 2007 06:51:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1775070AbXHMKvk (ORCPT ); Mon, 13 Aug 2007 06:51:40 -0400 Received: from mail.gmx.net ([213.165.64.20]:34213 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S941674AbXHMKvh (ORCPT ); Mon, 13 Aug 2007 06:51:37 -0400 Received: (qmail invoked by alias); 13 Aug 2007 10:51:34 -0000 Received: from R3460.r.pppool.de (EHLO noname) [89.54.52.96] by mail.gmx.net (mp039) with SMTP; 13 Aug 2007 12:51:34 +0200 X-Authenticated: #1490710 X-Provags-ID: V01U2FsdGVkX1+ziV1ZjTOzCUILvM0FrpyO4juGcuXQPs8TfmcfxU nFEW33V7OXBStc X-X-Sender: gene099@racer.site In-Reply-To: X-Y-GMX-Trusted: 0 Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Hi, On Sat, 11 Aug 2007, Steffen Prohaska wrote: > I'm impressed. Pretty much everything I tried today worked for me. After > I got git gui running, and learned how to avoid pitfalls of git > submodule, development went smoothly. Thanks! > I could also think of a fail safe update, that allows to upgrade an > existing msysgit to a specific tag (maybe after stashing the current > installation and reverting in case of problems). It's pretty early to think about stable releases, let alone upgrades ;-) > Maybe git gui could be integrated with the Windows Explorer and be > launched on a directory. Maybe this is one of your evil plans. But this > is already more than I need. That is already in the works. An alpha version is already working. > What do you think is needed to merge changes back to git.git? I counted > approximately 20k diff lines (incl. context) between msysgit's git > master and git.git's master. At a first glance much of them seem to be > compatibility stuff. It is _all_ compatibility stuff. Basically, it all boils down to grabbing a specific part of the diff related to a certain concept (such as NO_IPV6), and whip the patch (series) into shape. Submit it to git.git. Work on it until it is part of the official distribution. Continue with the next part of the diff. Ciao, Dscho