Re: ports on 10.0-CURRENT: r226027 is incorrect fix

On Mon, Oct 10, 2011 at 1:33 PM, Hartmann, O.
<ohartman@zedat.fu-berlin.de> wrote:
> On 10/10/11 21:04, Stanislav Sedov wrote:
>> On Sat, 8 Oct 2011 18:35:13 +0100
>> Chris Rees <utisoft@gmail.com> mentioned:
>>
>>> Last I heard, portmgr explicitly disapproved of this fix-- have I misse=
d
>>> something??? Erwin specifically said not to do it.
>>>
>>> Since when can anyone just commit stuff to bsd.port.mk, regardless of i=
ts
>>> location?
>>>
>>> This is a bad solution, please revert it or I will when I get back. We'=
re
>>> going to end up being asked to support it on ports@ otherwise.
>>>
>> You certianly missed something, including the rationale behind the portm=
gr@
>> descision of not committing to the ports tree (!) bsd.port.mk. =C2=A0Go =
find
>> some useful work to do like deleting old ports or whatever. =C2=A0You mi=
ght want
>> to consider deleting all mine ports, as I'm not going to support them an=
ymore
>> (after you backed out this fix without approval I don't have a working p=
orts
>> tree anymore on any of my 3 workstations).
>>
> Hello? Is there need for this barbarian rude tone?

Can everyone calm down a little bit, step back and think twice before
making reactions?  Stop it, as this hurts the project as a family.

Cheers,
--=20
Xin LI <delphij@delphij.net> https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"