From owner-freebsd-ports@FreeBSD.ORG  Sat Jan 25 18:41:23 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F071CFF7;
 Sat, 25 Jan 2014 18:41:23 +0000 (UTC)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
 by mx1.freebsd.org (Postfix) with ESMTP id 877A11861;
 Sat, 25 Jan 2014 18:41:23 +0000 (UTC)
Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net
 [76.21.10.192])
 by elvis.mu.org (Postfix) with ESMTPSA id 5EC641A3C19;
 Sat, 25 Jan 2014 10:41:23 -0800 (PST)
Message-ID: <52E40552.4010009@freebsd.org>
Date: Sat, 25 Jan 2014 10:41:22 -0800
From: Alfred Perlstein <alfred@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Baptiste Daroussin <bapt@FreeBSD.org>
Subject: Re: What is the problem with ports PR reaction delays?
References: <52E30990.2060903@marino.st> <52E33AA7.3080205@freebsd.org>
 <52E36BA1.5030900@marino.st> <52E37C16.5080901@freebsd.org>
 <52E3806D.4020902@marino.st> <52E3F03C.1060503@freebsd.org>
 <52E3F454.3020206@marino.st> <52E3F600.9020009@freebsd.org>
 <20140125180444.GD67191@ithaqua.etoilebsd.net> <52E40209.9060708@freebsd.org>
 <20140125183214.GC67763@ithaqua.etoilebsd.net>
In-Reply-To: <20140125183214.GC67763@ithaqua.etoilebsd.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John Marino <dragonflybsd@marino.st>, marino@freebsd.org,
 freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 18:41:24 -0000

On 1/25/14 10:32 AM, Baptiste Daroussin wrote:
> On Sat, Jan 25, 2014 at 10:27:21AM -0800, Alfred Perlstein wrote:
>> On 1/25/14 10:04 AM, Baptiste Daroussin wrote:
>>> On Sat, Jan 25, 2014 at 09:36:00AM -0800, Alfred Perlstein wrote:
>>>> On 1/25/14, 9:28 AM, John Marino wrote:
>>>>> On 1/25/2014 18:11, Alfred Perlstein wrote:
>>>>>> Still missing the point.  Git can sit on top of svn.
>>>>>>
>>>>> Other than converting SVN to Git, I don't know anything about that.  It
>>>>> would never be done in an official capacity.  Git is not an official
>>>>> tool of FreeBSD.
>>>>>
>>>> I encourage you to educate yourself then and then review the suggestions
>>>> I gave.
>>> I encourage you to give a shot at what you are suggesting. git-svn is broken for
>>> committers as long as it doesn't properly handle properties.
>> Or maybe our requirement for props is broken?
>>
>> Is $FreeBSD$ *that* important?
>>
>> -Alfred
> There is not only $Freebsd$ but also other props.

mergeinfo?

I'm wondering because there's huge projects out there not tied down to 
svn.  It seems to be a problem of our own invention.

Having managed the FreeNAS project for a year and exclusively using git 
we found ZERO use for any svn props.  We just used git and put all the 
cruft behind us.

And we were glad for it!

-Alfred