From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Sixt Subject: Re: Switching from CVS to GIT Date: Tue, 16 Oct 2007 08:29:32 +0200 Message-ID: <47145A4C.2070206@viscovery.net> References: <1192293466.17584.95.camel@homebase.localnet> <1192381040.4908.57.camel@homebase.localnet> <1773C6F0-87BE-4F3C-B68A-171E1F32E242@lrde.epita.fr> <47130B25.4010304@viscovery.net> <20071015231242.GR27899@spearce.org> <471455ED.8070408@viscovery.net> <20071016062144.GD13801@spearce.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: git list To: "Shawn O. Pearce" X-From: git-owner@vger.kernel.org Tue Oct 16 08:29:48 2007 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 1Ihfw2-0003pA-If for gcvg-git-2@gmane.org; Tue, 16 Oct 2007 08:29:47 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761793AbXJPG3f (ORCPT ); Tue, 16 Oct 2007 02:29:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760226AbXJPG3f (ORCPT ); Tue, 16 Oct 2007 02:29:35 -0400 Received: from lilzmailso02.liwest.at ([212.33.55.13]:10966 "EHLO lilzmailso02.liwest.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757320AbXJPG3e (ORCPT ); Tue, 16 Oct 2007 02:29:34 -0400 Received: from cm56-163-160.liwest.at ([86.56.163.160] helo=linz.eudaptics.com) by lilzmailso02.liwest.at with esmtpa (Exim 4.66) (envelope-from ) id 1Ihfve-0007lO-0G; Tue, 16 Oct 2007 08:29:22 +0200 Received: from [192.168.1.42] (J6T.linz.viscovery [192.168.1.42]) by linz.eudaptics.com (Postfix) with ESMTP id 1CC9E6B7; Tue, 16 Oct 2007 08:29:33 +0200 (CEST) User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <20071016062144.GD13801@spearce.org> X-Spam-Score: 1.7 (+) X-Spam-Report: ALL_TRUSTED=-1.8, BAYES_99=3.5 Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Shawn O. Pearce schrieb: > Johannes Sixt wrote: >>> Johannes Sixt wrote: >>>> Unfortunately, "Fetch" does not yet work[*] from within git-gui, so you >>>> have to fall back to git-fetch on the command line. >> It's the scripted fetch that does not work. The symptom is that the output ^^^^^^^^^^^^^^ >> of at least one of the commands (upload-pack, I think, because what I see >> is wire protocol) goes to a newly spawned console instead of wherever it >> was redirected to. >> >> I didn't bother reporting since builtin-fetch is on the way (which will >> hopefully make this a moot point) and our team here is comfortable with >> calling git fetch on the command line. > > Hmm. The way the builtin-fetch works this shouldn't happen, but > I'd appreciate it if you could test and report back before that > topic merges into master. This happens with git 1.5.3 plus the git-gui that comes with that. FWIW, I'm in the process of merging master of git.git into git/mingw.git, and then the builtin-fetch series (because on top of that there is my fork/exec removal series, which I'd like to adjust for Windows). And *then* I'll be able to report back to you. -- Hannes