From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: git-p4import.py robustness changes Date: Sat, 02 Jun 2007 14:33:25 -0700 Message-ID: <7vzm3inisa.fsf@assigned-by-dhcp.cox.net> References: <4ACE2ABC-8D73-4097-87AC-F3B27EDA97DE@slamb.org> <7vbqg01reo.fsf@assigned-by-dhcp.cox.net> <0EDF1E14-3682-4B1E-A7D2-F82388F752AA@slamb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: Scott Lamb X-From: git-owner@vger.kernel.org Sat Jun 02 23:33:34 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 1HubE6-0001ZH-5G for gcvg-git@gmane.org; Sat, 02 Jun 2007 23:33:34 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757724AbXFBVd1 (ORCPT ); Sat, 2 Jun 2007 17:33:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757781AbXFBVd1 (ORCPT ); Sat, 2 Jun 2007 17:33:27 -0400 Received: from fed1rmmtao106.cox.net ([68.230.241.40]:43175 "EHLO fed1rmmtao106.cox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756937AbXFBVd1 (ORCPT ); Sat, 2 Jun 2007 17:33:27 -0400 Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao106.cox.net (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20070602213327.DGIZ1540.fed1rmmtao106.cox.net@fed1rmimpo01.cox.net>; Sat, 2 Jun 2007 17:33:27 -0400 Received: from assigned-by-dhcp.cox.net ([68.5.247.80]) by fed1rmimpo01.cox.net with bizsmtp id 6lZR1X00C1kojtg0000000; Sat, 02 Jun 2007 17:33:26 -0400 In-Reply-To: <0EDF1E14-3682-4B1E-A7D2-F82388F752AA@slamb.org> (Scott Lamb's message of "Sat, 2 Jun 2007 13:41:55 -0700") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Scott Lamb writes: > On May 31, 2007, at 4:53 PM, Junio C Hamano wrote: > >> Actually, my preference is to have a "patch 0" before all of the >> above, that demotes git-p4import to contrib/ hierarchy. Having >> no access to p4 managed repositories (nor much inclination to >> get one), I can never test nor maintain it myself, so it is just >> crazy for me to be the maintainer for it. > > Will do. What does that mean for Documentation/git-p4import.txt and > the git-p4 rpm (defined in git.spec.in)? Should I move them with it? > (Seems nothing else in the main tree references contrib.) If so, > maybe I should set up a common "Documentation/asciidoc.mak" or > something for building the man/html pages rather than duplicating all > that Makefile logic. A much more preferable alternative is for you to say "Hey, don't say you want to demote it. I'll keep it maintained, I regularly use p4 and have a strong incentive to keep it working". Then we do not have to do the "patch 0" ;-)