Hi Junio, On Mon, 10 Dec 2018, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > Hi Kyle, > > > > On Sat, 8 Dec 2018, Kyle Meyer wrote: > > > >> Delete a misplaced word introduced by caafecfcf1 (rebase > >> --rebase-merges: adjust man page for octopus support, 2018-03-09). > >> > >> Signed-off-by: Kyle Meyer <kyle@xxxxxxxxxx> > > > > ACK. > > Thanks. > > > Too bad this did not make it into v2.20.0, but at least it can make it > > into a future version. > > The right way to fix it is to prepare a topic that can be merged > down to the 2.19.x track, and proceed normally to percolate it down > via 'next', 'master' and 'maint' as any other fixes. That is > already happening. > > The original documentation bug is older than where the 2.20 track > forked; the bug is in 2.19. Any such old bugs, users have survived > without it being fixed for a cycle already, and the fix is not that > urgent to interrupt the release engineering that is already underway > and redo it. > > A regression that appears only in -rc and a known bug in a new > feature that appears only in -rc are different matters. It is > prudent to always first access how serious they are and we must be > prepared to even delay the final as necessary. But I do not think > this one is. You are right, of course, this was not as critical a bug fix as others you integrated last minute. Thanks, Dscho
