On 2023-08-07 15:13, Fred Wright via devel wrote:
On Fri, 4 Aug 2023, James Browning via devel wrote:
On 08/04/2023 6:35 PM PDT Fred Wright via devel
wrote:
:::snip:::
I notice that the two commits for that don't seem to be in any branch.
Having commits only "owned" by a tag and not a bra
On Fri, 4 Aug 2023, James Browning via devel wrote:
On 08/04/2023 6:35 PM PDT Fred Wright via devel wrote:
:::snip:::
I notice that the two commits for that don't seem to be in any branch.
Having commits only "owned" by a tag and not a branch seems fragile.
I do not think it is particula
On 2023-08-07 14:34, Matthew Selsky wrote:
On Mon, Aug 07, 2023 at 02:14:40PM -0500, Richard Laager via devel wrote:
That said, I did advocate for merging it back in to master (as a no-op). But
I don't feel particularly strongly about that.
The code fix itself is already in master. I'll merg
On Mon, Aug 07, 2023 at 02:14:40PM -0500, Richard Laager via devel wrote:
> That said, I did advocate for merging it back in to master (as a no-op). But
> I don't feel particularly strongly about that.
The code fix itself is already in master. I'll merge the 1.2.2a NEWS into
master later this e
On 2023-08-04 20:35, Fred Wright via devel wrote:
I notice that the two commits for that don't seem to be in any branch.
Having commits only "owned" by a tag and not a branch seems fragile.
I think it's fine for a backport fix release like this.
That said, I did advocate for merging it back in
