Mailing List Archive

Andreas Metzler via Exim-dev <exim-dev@exim.org> (So 09 Mai 2021 08:06:11 CEST):
> Hello,
>
> there is a patch on exim-4.94+fixes which was applied after 4.94.2, it
> is therefore missing on exim-4.94.2+fixes.
>
> ed64b5c2f0f44db27ae48128fc97d5ad8406a28e Fix ${ipv6norm:}

Thank you, it is merged now into 4.94.2+fixes

--
Heiko

On 2021-05-09 Heiko Schlittermann via Exim-dev <exim-dev@exim.org> wrote:
> Andreas Metzler via Exim-dev <exim-dev@exim.org> (So 09 Mai 2021 08:06:11 CEST):
>> there is a patch on exim-4.94+fixes which was applied after 4.94.2, it
>> is therefore missing on exim-4.94.2+fixes.

>> ed64b5c2f0f44db27ae48128fc97d5ad8406a28e Fix ${ipv6norm:}

> Thank you, it is merged now into 4.94.2+fixes

Hello,

Thanks, seems to have happened again with
c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch
e.g. with a commit deleting all files?

cu Andreas

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

On 12/05/2021 19:08, Andreas Metzler via Exim-dev wrote:
> On 2021-05-09 Heiko Schlittermann via Exim-dev <exim-dev@exim.org> wrote:
>> Andreas Metzler via Exim-dev <exim-dev@exim.org> (So 09 Mai 2021 08:06:11 CEST):
> Thanks, seems to have happened again with
> c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch
> e.g. with a commit deleting all files?

You do realise that c1faf04 was only pushed about twenty minutes
before your mail?

I think I'll give up bothering to cherry-pick to
a +fixes branch at all, given the level of thanks we get.
--
Jeremy

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

On 2021-05-12 Jeremy Harris via Exim-dev <exim-dev@exim.org> wrote:
[...]
> I think I'll give up bothering to cherry-pick to
> a +fixes branch at all, given the level of thanks we get.

Good morning,

I am extremely grateful and care for the +fixes branches. I am very
sorry if my mail suggested I did not.

So here it is: Thanks for maintaining a +fixes branch.

cu Andreas

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

Good morning,

Andreas Metzler via Exim-dev <exim-dev@exim.org> (Mi 12 Mai 2021 20:08:52 CEST):
> Thanks, seems to have happened again with
> c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch
> e.g. with a commit deleting all files?

How to "close" a branch in Git?
There seem to be many ways.

I wouldn't feel comfortable with removing all files (even if we put
there a "README" about what happened.

Deleting the branch on "origin" won't help a lot, as I think, as if the
next one pushes to it again, it will be re-surrected, won't it?

I think, renaming it to "archive/exim-4.94+fixes" or so would have the
same effect, as soon as someone pushes to "exim-4.94+fixes" again, the
the branch will be there again.

Can we have a branch "read only" in Git? (Using hooks on the repo can do
something like this for sure, but that's not the way I'd like to go.)

Does Git have a special commit which marks this branch as "closed"
and rejects any further commits on this branch?

--
Heiko

Andreas Metzler via Exim-dev <exim-dev@exim.org> (Mi 12 Mai 2021 20:08:52 CEST):
> On 2021-05-09 Heiko Schlittermann via Exim-dev <exim-dev@exim.org> wrote:
>
> Thanks, seems to have happened again with
> c1faf04b865465894c7ca41ab4585fb69d4a5936. How about closing this branch
> e.g. with a commit deleting all files?

I merged 4.94+fixes into 4.94.2+fixes (again).

--
Heiko

Heiko Schlittermann via Exim-dev <exim-dev@exim.org> (Do 13 Mai 2021 10:13:31 CEST):
> I merged 4.94+fixes into 4.94.2+fixes (again).
Not pushed yet, it's running the testsuite locally.
--
Heiko