On 2022-04-08 20:25, Kyle Evans wrote:
Hello!
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching this to the GNU behavior,
which feels a whole lot more reasonable. Notably, they'll only
On 2022-04-09 03:25, Kyle Evans wrote:
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching this to the GNU behavior,
which feels a whole lot more reasonable. Notably, they'll only create
b
On Sun, Apr 10, 2022 at 10:48 AM Gary Jennejohn wrote:
>
> On Sun, 10 Apr 2022 10:21:56 -0500
> Kyle Evans wrote:
>
> > On Sun, Apr 10, 2022 at 5:33 AM Matthias Andree
> > wrote:
> [big SNIP]
> > > I checked POSIX 2018, apparently the backup files (.orig) are only
> > > required if -b is given,
On Sun, Apr 10, 2022 at 5:33 AM Matthias Andree wrote:
>
> [resending from hopefully subscribed address that it makes it to some of
> the lists]
>
> Am 09.04.22 um 05:25 schrieb Kyle Evans:
> > Hello!
> >
> > FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
> > where a backup i
[resending from hopefully subscribed address that it makes it to some of
the lists]
Am 09.04.22 um 05:25 schrieb Kyle Evans:
Hello!
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching th
In message
, Kyle Evans writes:
> On Fri, Apr 8, 2022 at 10:41 PM Warner Losh wrote:
> >
> >
> >
> > On Fri, Apr 8, 2022, 9:26 PM Kyle Evans wrote:
> >>
> >> Hello!
> >>
> >> FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
> >> where a backup is created for every file patche
On Fri, Apr 8, 2022 at 10:41 PM Warner Losh wrote:
>
>
>
> On Fri, Apr 8, 2022, 9:26 PM Kyle Evans wrote:
>>
>> Hello!
>>
>> FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
>> where a backup is created for every file patched.
>>
>> I'd like to test the waters on switching thi
On Fri, Apr 8, 2022, 9:26 PM Kyle Evans wrote:
> Hello!
>
> FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
> where a backup is created for every file patched.
>
> I'd like to test the waters on switching this to the GNU behavior,
> which feels a whole lot more reasonable. No
Hello!
FreeBSD's patch follows historical patch(1) behavior w.r.t. backups,
where a backup is created for every file patched.
I'd like to test the waters on switching this to the GNU behavior,
which feels a whole lot more reasonable. Notably, they'll only create
backup files if a mismatch was det
