From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758336AbXIBXQ7 (ORCPT ); Sun, 2 Sep 2007 19:16:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754701AbXIBXQs (ORCPT ); Sun, 2 Sep 2007 19:16:48 -0400 Received: from bay0-omc1-s1.bay0.hotmail.com ([65.54.246.73]:58941 "EHLO bay0-omc1-s1.bay0.hotmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754395AbXIBXQr (ORCPT ); Sun, 2 Sep 2007 19:16:47 -0400 X-Originating-IP: [64.231.205.174] X-Originating-Email: [seanlkml@sympatico.ca] Date: Sun, 2 Sep 2007 19:16:44 -0400 From: Sean To: Junio C Hamano Cc: "H. Peter Anvin" , David Kastrup , git@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [ANNOUNCE] GIT 1.5.3 Message-Id: <20070902191644.29d46cd2.seanlkml@sympatico.ca> In-Reply-To: <7v4picpvgq.fsf@gitster.siamese.dyndns.org> References: <7vodglr32i.fsf@gitster.siamese.dyndns.org> <46DA5F33.2020005@zytor.com> <85odgltrtj.fsf@lola.goethe.zz> <46DA88EF.7080103@zytor.com> <20070902133803.1b46f599.seanlkml@sympatico.ca> <7v4picpvgq.fsf@gitster.siamese.dyndns.org> X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.14; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Sep 2007 23:17:51.0375 (UTC) FILETIME=[7BB731F0:01C7EDB7] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 02 Sep 2007 15:13:09 -0700 Junio C Hamano wrote: Hi Junio, > For majority of general public, I thought the spec file _I_ > ship, along with RPM files _I_ build, are contrib status > already. Don't distro people do their own RPM packages, instead > of using what I placed on k.org? Didn't know you used RPM yourself, so I guess this is just a case of something slipping through rather than the spec file needing a maintainer. Having said that, it seems odd that you would say the spec file included with git is "contrib status already". How can something be contrib status unless it is in the contrib directory of Git? > Assuming that we do not give the old git-p4import script > packaged in "git-p4 package", would the following patch be all > that is needed, or do we need other things in the spec file? Given the comment from David, I suspect your patch is all that's needed; hopefully Peter can give it a quick test. Sean