Date: Fri, 3 May 2019 13:59:49 -0600 From: Adam Weinberger <adamw@adamw.org> To: Jan Beich <jbeich@freebsd.org> Cc: Stefan Bethke <stb@lassitu.de>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Gitea update to 1.8 breaking config change Message-ID: <CAP7rwcg2NgELU27r-ZA2OP8H8YX2ap-bK2KT%2BrWie2yUvPkiaw@mail.gmail.com> In-Reply-To: <5zqr-9vpt-wny@FreeBSD.org> References: <6E748C6E-F223-49B8-B5A8-0156ADCC452B@lassitu.de> <5zqr-9vpt-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 3, 2019 at 1:36 PM Jan Beich <jbeich@freebsd.org> wrote: > > Stefan Bethke <stb@lassitu.de> writes: > > > For those of you using Gitea a quick heads-up: > [...] > > The proper place to document breaking changes is UPDATING file. > ports@ list has low signal-to-noise ratio but high traffic, so your > heads-up maybe forgotten before the next /quarterly branches. > > https://www.freebsd.org/doc/en/books/porters-handbook/moved-and-updating-files.html Jan is correct, but a breaking change like this should also go into the pkg-message for the gitea port. # Adam -- Adam Weinberger adamw@adamw.org https://www.adamw.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP7rwcg2NgELU27r-ZA2OP8H8YX2ap-bK2KT%2BrWie2yUvPkiaw>