New `--reapply-cherry-picks` warning
- From
- Σταύρος Ντέντος <stdedos@gmail.com>
- Date
- Feb 2, 2022, 08:56 UTC
- Message-ID
- <CAHMHMxUZpR8MBj+9mSb1Cr3PBCsAx=6zLo9mKpeD_ehqDP4nvQ@mail.gmail.com>
Hello there,
I have noticed the new warning that's coming in the https://github.com/git/git/commit/767a4ca648f8791c1fb623bd9f79fd8d7f026499
I am currently using the `[pull] rebase = true` option; and basically that warning is also coming every time I am pulling. I have tried doing `git pull --reapply-cherry-picks`; however, it seems that the `git pull` cannot pass options to the underlying `git rebase` invocation.
I noticed that there is no way to "set" the `--reapply-cherry-picks` in the gitconfig options.
I prefer the rebase backend for the `git pull`; however, I see no way of doing "what I want", with the exception of: git fetch --all ; git rebase --reapply-cherry-picks
Which is two steps, technically.
Also with every rebase I am doing, I'd have to remember that. And it is probably not possible (by design) to do `alias.rebase = rebase --reapply-cherry-picks` - which I understand. (however, allowing aliases like `alias.x = x --cmd-opts` does not sound "so bad" with me)
Would you consider adding a configuration option for the `--reapply-cherry-picks`?
With regards, Ntentos Stavros