;>> Changes by: k...@cvs.openbsd.org 2024/10/06 04:24:24
>>>>
>>>> Modified files:
>>>> infrastructure/mk: bsd.port.mk
>>>>
>>>> Log message:
>>>> new opt-in PATCH_QUIET aka. patch(1) -s; OK tb
>>>
>>> Was
24/10/06 04:24:24
> >>
> >> Modified files:
> >>infrastructure/mk: bsd.port.mk
> >>
> >> Log message:
> >> new opt-in PATCH_QUIET aka. patch(1) -s; OK tb
> >
> > Was this discussed somewhere? We could have simply brought PATCH_DEBUG
> >
06.10.2024 23:10, Christian Weisgerber пишет:
> Klemens Nanni:
>
>> CVSROOT: /cvs
>> Module name: ports
>> Changes by: k...@cvs.openbsd.org2024/10/06 04:24:24
>>
>> Modified files:
>> infrastructure/mk: bsd.port.mk
>>
>> Log me
Klemens Nanni:
> CVSROOT: /cvs
> Module name: ports
> Changes by: k...@cvs.openbsd.org2024/10/06 04:24:24
>
> Modified files:
> infrastructure/mk: bsd.port.mk
>
> Log message:
> new opt-in PATCH_QUIET aka. patch(1) -s; OK tb
Was this discusse
.Cm update-patches
creating useless churn !
+.It Ev PATCH_QUIET
+User settings.
+If set to
+.Sq Yes ,
+.Ev PATCH
+will work quietly.
.It Ev PATCH_STRIP
Patch option used to strip directory levels while applying port's patches.
Defaults to -p0.
> I dislike the noisiness of our patch
On Tue, Oct 01, 2024 at 09:39:19PM +, Klemens Nanni wrote:
> I don't like flooding terminal backlog with stuff I already no.
>
> Our patch(1) is generally quite verbose, but this helps a lot:
>
> -s, --quiet, --silent
> Makes patch do its work silently, unless an error occur
1 instead of 61 lines.
$ make extract >/dev/null
$ make PATCH_QUIET=yes patch
===> Patching for git-2.46.2
===> Applying OpenBSD patch patch-builtin_gc_c
===> Ignoring patchfile patch-builtin_gc_c.orig
===> Applying OpenBSD patch patch-config_mak_uname
===> Ignoring patc