Le 14/01/2017 à 18:02, Julian Elischer a écrit :
> On 4/01/2017 4:05 AM, Kurt Jaeger wrote:
>> Hi!
>>
>>> I got several "yes please" from members of the public,
>>> but no actionable response from members of the ports group
>>> So I am asking again.
>> I'd also like to have this patch.
>>
>> If I l
On 4/01/2017 4:05 AM, Kurt Jaeger wrote:
Hi!
I got several "yes please" from members of the public,
but no actionable response from members of the ports group
So I am asking again.
I'd also like to have this patch.
If I look at the PR, mat is already working to integrate it.
yes though I've
Hi!
> I got several "yes please" from members of the public,
> but no actionable response from members of the ports group
> So I am asking again.
I'd also like to have this patch.
If I look at the PR, mat is already working to integrate it.
--
p...@opsec.eu+49 171 3101372
jul...@freebsd.org (Julian Elischer) writes:
>Sometime ago I proposed the following change.
>I got several "yes please" from members of the public,
>but no actionable response from members of the ports group
>So I am asking again.
>> +# EXTRA_PATCH_TREE - where to find extra 'out-of-tree' patche
On 3/01/2017 6:44 PM, Vlad K. wrote:
On 2017-01-03 11:31, Julian Elischer wrote:
Sometime ago I proposed the following change.
I got several "yes please" from members of the public,
but no actionable response from members of the ports group
So I am asking again.
I haven't checked the code in
On 3/01/2017 6:31 PM, Julian Elischer wrote:
Sometime ago I proposed the following change.
I got several "yes please" from members of the public,
but no actionable response from members of the ports group
So I am asking again.
As a src committer I don't feel qualified to do the commit myself
a
On 2017-01-03 11:31, Julian Elischer wrote:
Sometime ago I proposed the following change.
I got several "yes please" from members of the public,
but no actionable response from members of the ports group
So I am asking again.
I haven't checked the code in detail for correctness, but conceptua
Sometime ago I proposed the following change.
I got several "yes please" from members of the public,
but no actionable response from members of the ports group
So I am asking again.
As a src committer I don't feel qualified to do the commit myself and
would like a guide/mentor for the task if I
On Sat, May 14, 2016 at 11:25:08AM +0800, Julian Elischer wrote:
> so who or what decides if I can put this in?
portmgr. From the portmgr pages:
Changes to bsd.port.mk are not the only commits that can have a drastic
effect on the tree. We request that any such changes also be tested on
th
On 13/05/2016 12:11 AM, Julian Elischer wrote:
so who or what decides if I can put this in? As a long term committer
from before there were ports, do I have access to it?
do I need to get a ports mentor? (seems likely and would make sense)..
do I apply somewhere? Or should I look for soemone i
On 13/05/2016 3:26 PM, Andrzej Tobola wrote:
On Fri, May 13, 2016 at 12:11:47AM +0800, Julian Elischer wrote:
This patch is pretty self explanatory.
it allows us to keep patches for various ports separately in a sparse
hierarchy while not having to write to the ports tree itself.
In case the l
On Fri, May 13, 2016 at 12:11:47AM +0800, Julian Elischer wrote:
> This patch is pretty self explanatory.
>
> it allows us to keep patches for various ports separately in a sparse
> hierarchy while not having to write to the ports tree itself.
>
> In case the list scrubs hte text attachment (dif
On 13/05/2016 3:19 AM, Julian H. Stacey wrote:
Julian Elischer wrote:
This patch is pretty self explanatory.
it allows us to keep patches for various ports separately in a sparse
hierarchy while not having to write to the ports tree itself.
Nice idea ! I'll have a look.
BTW I've had something
Julian Elischer wrote:
>
> This patch is pretty self explanatory.
>
> it allows us to keep patches for various ports separately in a sparse
> hierarchy while not having to write to the ports tree itself.
Nice idea ! I'll have a look.
BTW I've had something somewhat similar for maybe a decade or
On Fri, 13 May 2016 00:11:47 +0800 Julian Elischer wrote
> This patch is pretty self explanatory.
>
> it allows us to keep patches for various ports separately in a sparse
> hierarchy while not having to write to the ports tree itself.
>
> In case the list scrubs hte text attachment (diff) her
This patch is pretty self explanatory.
it allows us to keep patches for various ports separately in a sparse
hierarchy while not having to write to the ports tree itself.
In case the list scrubs hte text attachment (diff) here's the
description part of the diff.
> //depot/bugatti/FreeBS
16 matches
Mail list logo
