My two cents...
I think some of the integration issues can be resolved with some rule
changes and showing those relevant rules that people will see every time
they make a pull request, report, etc... as I think what will happen with
each item is too uncertain even if there was automation. I think
On Tue, Jan 31, 2023, 9:47 AM David Chisnall wrote:
>
> On 30/01/2023 21:39, Yetoo wrote:
> >
> > If github is going to be considered for issue tracking I just want to
> > say, after having extensively using it for issue tracking, it tends to
> > be difficult to fi
On Tue, May 30, 2023 at 8:36 AM bob prohaska wrote:
>
> On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
> >
> > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06
> > -0700):
> >
> > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
> > > >
> > > > The question is how
In https://docs.freebsd.org/en/books/handbook/cutting-edge/ I can see that
at* 24.5.6.1 Merging Configuration Files* are instructions to bootstrap
etcupdate if switching from mergemaster. This is really convenient and
really useful, *EXCEPT* for that fact that it is placed in a part of the
handbook
If it was in a temporary directory, even if I manaually resolved the file
and merge, I was expecting that file marked as resolve to stay in that
temporary directory until I was done with all my files. Maybe I'm confusing
mergemaster -Ui behavior with something else, but it seems like only
merging a
On Fri, Dec 3, 2021 at 3:52 AM Yetoo Happy wrote:
>
> In https://docs.freebsd.org/en/books/handbook/cutting-edge/ I can see that at
> 24.5.6.1 Merging Configuration Files are instructions to bootstrap etcupdate
> if switching from mergemaster. This is really convenient and r
