[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stable/2.22 has branched; master is 2.23.0
From: |
Carl Sorensen |
Subject: |
Re: stable/2.22 has branched; master is 2.23.0 |
Date: |
Fri, 16 Oct 2020 12:46:11 -0600 |
On Fri, Oct 16, 2020 at 11:41 AM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>
> So master is 2.23.0 and usual development can resume, with the pleading
> to avoid disruptive changes that make picking harder than necessary.
> Fixes should also go to master and I'll pick them to the branch. If you
> really need to do that, please use 'git cherry-pick -x' to record the
> original hash.
>
>
When do we stop worrying about cherry-picking and feel free to make
disruptive changes again? I'm not asking because I have something in the
queue; I'm just trying to understand the policy.
Thanks,
Carl
- Re: stable/2.22 has branched; master is 2.23.0, (continued)
- Re: stable/2.22 has branched; master is 2.23.0, Jean-Charles Malahieude, 2020/10/21
- Re: stable/2.22 has branched; master is 2.23.0, Jonas Hahnfeld, 2020/10/21
- Re: stable/2.22 has branched; master is 2.23.0, Jean-Charles Malahieude, 2020/10/26
- Re: stable/2.22 has branched; master is 2.23.0, Jonas Hahnfeld, 2020/10/26
- Re: stable/2.22 has branched; master is 2.23.0, Jean-Charles Malahieude, 2020/10/27
- Re: stable/2.22 has branched; master is 2.23.0, Jonas Hahnfeld, 2020/10/27
- Re: stable/2.22 has branched; master is 2.23.0, Jean Abou Samra, 2020/10/21
- Re: stable/2.22 has branched; master is 2.23.0, Jonas Hahnfeld, 2020/10/24
- Re: stable/2.22 has branched; master is 2.23.0, Jean-Charles Malahieude, 2020/10/24
- Re: stable/2.22 has branched; master is 2.23.0, Jonas Hahnfeld, 2020/10/24
Re: stable/2.22 has branched; master is 2.23.0,
Carl Sorensen <=