On Sun, May 17, 2020 at 3:10 PM Trevor wrote:
>
> Carl Sorensen wrote 17/05/2020 18:32:27
>> It seems to me that there are at least two possibilities for how this
>> should be handled.
>>
>> 1) Once an issue is accepted and pushed, if there are problems
>> resulting from the issue, a new issue
Carl Sorensen wrote 17/05/2020 18:32:27
I've been verifying issues from 2.21.1.
This has raised a need for clarification about how we handle issues
once they have been pushed.
It seems to me that there are at least two possibilities for how this
should be handled.
1) Once an issue is
Am Sonntag, den 17.05.2020, 19:43 +0200 schrieb David Kastrup:
> Carl Sorensen writes:
>
> > Dear team,
> >
> > I've been verifying issues from 2.21.1.
> >
> > This has raised a need for clarification about how we handle issues
> > once they have been pushed.
> >
> > Consider issue 5890:
> >
On 17/05/2020 18:43, David Kastrup wrote:
New issue + crossreference would be my suggestion.
and mine.
James
Carl Sorensen writes:
> Dear team,
>
> I've been verifying issues from 2.21.1.
>
> This has raised a need for clarification about how we handle issues
> once they have been pushed.
>
> Consider issue 5890: https://gitlab.com/lilypond/lilypond/-/issues/5890
>
> The issue was fixed and a solution
Dear team,
I've been verifying issues from 2.21.1.
This has raised a need for clarification about how we handle issues
once they have been pushed.
Consider issue 5890: https://gitlab.com/lilypond/lilypond/-/issues/5890
The issue was fixed and a solution was pushed.
Then, Dan recognized that
