{"thread":{"id":"49980","subject":"[PATCH] rebase docs: drop stray word in merge command description","startedAt":"2018-12-08T23:15:56Z","lastAt":"2018-12-10T08:27:56Z","messageCount":4,"participants":["Kyle Meyer","Johannes Schindelin","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"364821","messageId":"20181208231541.1341999-1-kyle@kyleam.com","threadId":"49980","inReplyTo":null,"subject":"[PATCH] rebase docs: drop stray word in merge command description","fromName":"Kyle Meyer","fromEmail":"kyle@kyleam.com","sentAt":"2018-12-08T23:15:41Z","receivedAt":"2018-12-08T23:15:56Z","isPatch":true,"sender":{"key":"kyle@kyleam.com","avatar":"https://avatars.githubusercontent.com/u/1297788?v=4"},"body":"Delete a misplaced word introduced by caafecfcf1 (rebase\n--rebase-merges: adjust man page for octopus support, 2018-03-09).\n\nSigned-off-by: Kyle Meyer \n---\n Documentation/git-rebase.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\nindex dff17b3178..2ee535fb23 100644\n--- a/Documentation/git-rebase.txt\n+++ b/Documentation/git-rebase.txt\n@@ -979,7 +979,7 @@ when the merge operation did not even start), it is rescheduled immediately.\n \n At this time, the `merge` command will *always* use the `recursive`\n merge strategy for regular merges, and `octopus` for octopus merges,\n-strategy, with no way to choose a different one. To work around\n+with no way to choose a different one. To work around\n this, an `exec` command can be used to call `git merge` explicitly,\n using the fact that the labels are worktree-local refs (the ref\n `refs/rewritten/onto` would correspond to the label `onto`, for example).\n-- \n2.19.2\n\n"},{"id":"364870","messageId":"nycvar.QRO.7.76.6.1812092040320.43@tvgsbejvaqbjf.bet","threadId":"49980","inReplyTo":"20181208231541.1341999-1-kyle@kyleam.com","subject":"Re: [PATCH] rebase docs: drop stray word in merge command description","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2018-12-09T19:41:15Z","receivedAt":"2018-12-09T19:41:20Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Kyle,\n\nOn Sat, 8 Dec 2018, Kyle Meyer wrote:\n\n> Delete a misplaced word introduced by caafecfcf1 (rebase\n> --rebase-merges: adjust man page for octopus support, 2018-03-09).\n> \n> Signed-off-by: Kyle Meyer \n\nACK.\n\nToo bad this did not make it into v2.20.0, but at least it can make it\ninto a future version.\n\nThanks,\nJohannes\n\n> ---\n> Documentation/git-rebase.txt | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n> \n> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\n> index dff17b3178..2ee535fb23 100644\n> --- a/Documentation/git-rebase.txt\n> +++ b/Documentation/git-rebase.txt\n> @@ -979,7 +979,7 @@ when the merge operation did not even start), it is rescheduled immediately.\n> \n> At this time, the `merge` command will *always* use the `recursive`\n> merge strategy for regular merges, and `octopus` for octopus merges,\n> -strategy, with no way to choose a different one. To work around\n> +with no way to choose a different one. To work around\n> this, an `exec` command can be used to call `git merge` explicitly,\n> using the fact that the labels are worktree-local refs (the ref\n> `refs/rewritten/onto` would correspond to the label `onto`, for example).\n> -- \n> 2.19.2\n> \n> \n"},{"id":"364897","messageId":"xmqqk1ki2h32.fsf@gitster-ct.c.googlers.com","threadId":"49980","inReplyTo":"nycvar.QRO.7.76.6.1812092040320.43@tvgsbejvaqbjf.bet","subject":"Re: [PATCH] rebase docs: drop stray word in merge command description","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-12-10T03:31:13Z","receivedAt":"2018-12-10T03:31:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> Hi Kyle,\n>\n> On Sat, 8 Dec 2018, Kyle Meyer wrote:\n>\n>> Delete a misplaced word introduced by caafecfcf1 (rebase\n>> --rebase-merges: adjust man page for octopus support, 2018-03-09).\n>> \n>> Signed-off-by: Kyle Meyer \n>\n> ACK.\n\nThanks.\n\n> Too bad this did not make it into v2.20.0, but at least it can make it\n> into a future version.\n\nThe right way to fix it is to prepare a topic that can be merged\ndown to the 2.19.x track, and proceed normally to percolate it down\nvia 'next', 'master' and 'maint' as any other fixes. That is\nalready happening.\n\nThe original documentation bug is older than where the 2.20 track\nforked; the bug is in 2.19. Any such old bugs, users have survived\nwithout it being fixed for a cycle already, and the fix is not that\nurgent to interrupt the release engineering that is already underway\nand redo it.\n\nA regression that appears only in -rc and a known bug in a new\nfeature that appears only in -rc are different matters. It is\nprudent to always first access how serious they are and we must be\nprepared to even delay the final as necessary. But I do not think\nthis one is.\n"},{"id":"364908","messageId":"nycvar.QRO.7.76.6.1812100927150.43@tvgsbejvaqbjf.bet","threadId":"49980","inReplyTo":"xmqqk1ki2h32.fsf@gitster-ct.c.googlers.com","subject":"Re: [PATCH] rebase docs: drop stray word in merge command description","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2018-12-10T08:27:50Z","receivedAt":"2018-12-10T08:27:56Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Mon, 10 Dec 2018, Junio C Hamano wrote:\n\n> Johannes Schindelin writes:\n> \n> > Hi Kyle,\n> >\n> > On Sat, 8 Dec 2018, Kyle Meyer wrote:\n> >\n> >> Delete a misplaced word introduced by caafecfcf1 (rebase\n> >> --rebase-merges: adjust man page for octopus support, 2018-03-09).\n> >> \n> >> Signed-off-by: Kyle Meyer \n> >\n> > ACK.\n> \n> Thanks.\n> \n> > Too bad this did not make it into v2.20.0, but at least it can make it\n> > into a future version.\n> \n> The right way to fix it is to prepare a topic that can be merged\n> down to the 2.19.x track, and proceed normally to percolate it down\n> via 'next', 'master' and 'maint' as any other fixes. That is\n> already happening.\n> \n> The original documentation bug is older than where the 2.20 track\n> forked; the bug is in 2.19. Any such old bugs, users have survived\n> without it being fixed for a cycle already, and the fix is not that\n> urgent to interrupt the release engineering that is already underway\n> and redo it.\n> \n> A regression that appears only in -rc and a known bug in a new\n> feature that appears only in -rc are different matters. It is\n> prudent to always first access how serious they are and we must be\n> prepared to even delay the final as necessary. But I do not think\n> this one is.\n\nYou are right, of course, this was not as critical a bug fix as others you\nintegrated last minute.\n\nThanks,\nDscho\n"}]}