You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
@etkaar since this is already a duplicate of #2565, why not just force push to the branch of this PR? This topic already has a number of duplicate issues and PRs, no need to make more, IMO.
You can still keep this current work in a branch on your Github fork, Git lets you branch off of branches and/or rename branches. Something like:
# backup the current version
$ git branch -m always_set_from_selected always_set_from_selected_pref
# make a new branch off of master with the same name as this PR branch
$ git checkout -b always_set_from_selected master
# use my patch (or edit the files manually)
$ git apply <file_containing_my_patch_above>
# ...do other changes, commits, etc.
# force push to this branch to update this PR
$ git push <your remote/fork name> +always_set_from_selected
# if you want the backed up version on Github too
$ git push <your remote/fork name> always_set_from_selected_pref—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.