lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handling problems with patches after the patch is pushed


From: Carl Sorensen
Subject: Re: Handling problems with patches after the patch is pushed
Date: Sun, 17 May 2020 15:33:08 -0600

On Sun, May 17, 2020 at 3:10 PM Trevor <address@hidden> wrote:
>
> Carl Sorensen wrote 17/05/2020 18:32:27
<snip>
>> 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 should be created. This lets
>> the original issue stand as fixed.
>>
<snip>
> I definitely prefer (1). I think (2) would potentially run into a variety of
> further problems, and would make for a confusing trail if it needed
> to be followed later. Maybe a comment and pointer could be added
> to the first issue to indicate the continuation of the fix.
>

There have been enough people responding positively to my preferred
solution of (1) that I have gone ahead and done that in this issue.

Issue #5890 is now verified, and all of 2.21.1 has now been verified.

Thanks,

Carl



reply via email to

[Prev in Thread] Current Thread [Next in Thread]