[PATCH v3] rebase: clarify --reschedule-failed-exec default
- From
Illia Bobyr <illia.bobyr@gmail.com>
- Date
- Jan 5, 2024, 01:14 UTC
- Message-ID
- <20240105011424.1443732-1-illia.bobyr@gmail.com>
- In-Reply-To
- <ZZcE/Kw24YKlqSOT@nand.local>
Sorry, I did not actually include the change in v2. Still learning how to use git send-email.
On Thu, Jan 04, 2024 at 11:20:28AM -0800, Taylor Blau wrote:
Show 14 quoted lines
> [...] > > > +Recording this option for the whole rebase is a convenience feature. Otherwise > > +an explicit `--no-reschedule-failed-exec` at the start would be overridden by > > +the presence of a `rebase.rescheduleFailedExec=true` configuration when `git > > +rebase --continue` is invoked. Currently, you can not, pass > > +`--[no-]reschedule-failed-exec` to `git rebase --continue`. > > The last sentence was a bit confusing to me. I assume you meant > > Currently, you cannot pass `--[no-]reschedule-failed-exec` [...] > > without the comma between "pass" and "`--[no]reschedule-failed-exect`", > and replacing "can not" with "cannot".
Applied. Thank you for reviewing!