From: Alex Henrie <alexhenrie24@gmail.com>
To: git@vger.kernel.org, tao@klerks.biz, gitster@pobox.com,
newren@gmail.com, phillip.wood123@gmail.com,
Johannes.Schindelin@gmx.de, sorganov@gmail.com,
chooglen@google.com, calvinwan@google.com,
jonathantanmy@google.com
Cc: Alex Henrie <alexhenrie24@gmail.com>
Subject: [PATCH v7 0/3] rebase: document, clean up, and introduce a config option for --rebase-merges
Date: Sun, 12 Mar 2023 15:04:53 -0600 [thread overview]
Message-ID: <20230312210456.92364-1-alexhenrie24@gmail.com> (raw)
In-Reply-To: <20230305050709.68736-1-alexhenrie24@gmail.com>
This patch series introduces a rebase.rebaseMerges config option to
accommodate users who would like --rebase-merges to be on by default and
to facilitate turning on --rebase-merges by default without
configuration in a future version of Git. It also cleans up and
documents the behavior of the --rebase-merges command line option to
avoid confusion about how the config option and the command line option
interact.
Changes from v6:
- Don't say that the default rebase-merges mode will likely change to
rebase-cousins (although it might change to something else)
- In git-config.txt, say that rebase.rebaseMerges=true is equivalent
to --rebase-merges=no-rebase-cousins
- Add a link from the revised paragraph in git-rebase.txt to the
corresponding new section in git-config.txt
- Clear rebase_cousins if rebase.rebaseMerges is set to true after
having been set to rebase-cousins or no-rebase-cousins
- Actually remove the test for --rebase-merges=""
- Remove the test for --rebase-merges=no-rebase-cousins overriding
rebase.rebaseMerges=rebase-cousins
Suggestions on v6 not incorporated in v7:
- Make --rebase-merges without an argument clobber the mode specified in
rebase.rebaseMerges
- In the tests, pass --force and check the graph itself or the reflog
instead of checking that the graph has not changed by checking that
the commit hash has not changed
- Add --rebase-merges=on as a synonym of
--rebase-merges=no-rebase-cousins and --rebase-merges=off as a synonym
of --no-rebase-merges
- Rewrite the documentation for rebase-cousins to more clearly explain
the difference between rebase-cousins and no-rebase-cousins
Thanks to Phillip, Junio, Glen, and Sergey for your feedback on v6.
Alex Henrie (3):
rebase: add documentation and test for --no-rebase-merges
rebase: deprecate --rebase-merges=""
rebase: add a config option for --rebase-merges
Documentation/config/rebase.txt | 11 ++++
Documentation/git-rebase.txt | 20 ++++---
builtin/rebase.c | 76 +++++++++++++++++++-------
t/t3422-rebase-incompatible-options.sh | 17 ++++++
t/t3430-rebase-merges.sh | 58 ++++++++++++++++++++
5 files changed, 156 insertions(+), 26 deletions(-)
Range-diff against v6:
1: bf08c03ba7 = 1: 3aee0c2277 rebase: add documentation and test for --no-rebase-merges
2: 26f98b8400 = 2: e57843d8b5 rebase: deprecate --rebase-merges=""
3: 402365256c ! 3: b0c1a4dcb2 rebase: add a config option for --rebase-merges
@@ Commit message
.gitconfig.
In the future, the default rebase-merges mode may change from
- no-rebase-cousins to rebase-cousins. Support setting rebase.rebaseMerges
- to the nonspecific value "true" for users who do not need or want to
- care about the default changing in the future. Similarly, for users who
- have --rebase-merges in an alias and want to get the future behavior
- now, use the specific rebase-merges mode from the config if a specific
- mode is not given on the command line.
+ no-rebase-cousins to some other mode that doesn't exist yet. Support
+ setting rebase.rebaseMerges to the nonspecific value "true" for users
+ who do not need or want to care about the default changing in the
+ future. Similarly, for users who have --rebase-merges in an alias and
+ want to get the future behavior now, use the specific rebase-merges mode
+ from the config if a specific mode is not given on the command line.
Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
@@ Documentation/config/rebase.txt: rebase.rescheduleFailedExec::
+rebase.rebaseMerges::
+ Whether and how to set the `--rebase-merges` option by default. Can
+ be `rebase-cousins`, `no-rebase-cousins`, or a boolean. Setting to
-+ true is equivalent to `--rebase-merges` without an argument, setting to
-+ `rebase-cousins` or `no-rebase-cousins` is equivalent to
-+ `--rebase-merges` with that value as its argument, and setting to false
-+ is equivalent to `--no-rebase-merges`. Passing `--rebase-merges` on the
++ true or to `no-rebase-cousins` is equivalent to
++ `--rebase-merges=no-rebase-cousins`, setting to `rebase-cousins` is
++ equivalent to `--rebase-merges=rebase-cousins`, and setting to false is
++ equivalent to `--no-rebase-merges`. Passing `--rebase-merges` on the
+ command line without an argument overrides a `rebase.rebaseMerges=false`
+ configuration, but the absence of a specific rebase-merges mode on the
+ command line does not counteract a specific mode set in the configuration.
@@ Documentation/git-rebase.txt: See also INCOMPATIBLE OPTIONS below.
-such commits are instead rebased onto `<upstream>` (or `<onto>`, if
-specified).
+`no-rebase-cousins`. If the mode is not specified on the command line or in
-+the `rebase.rebaseMerges` config option, it defaults to `no-rebase-cousins`.
-+In `no-rebase-cousins` mode, commits which do not have `<upstream>` as direct
++the `rebase.rebaseMerges` config option (see linkgit:git-config[1] or
++"CONFIGURATION" below), it defaults to `no-rebase-cousins`. In
++`no-rebase-cousins` mode, commits which do not have `<upstream>` as direct
+ancestor will keep their original branch point, i.e. commits that would be
+excluded by linkgit:git-log[1]'s `--ancestry-path` option will keep their
+original ancestry by default. In `rebase-cousins` mode, such commits are
@@ builtin/rebase.c: static int rebase_config(const char *var, const char *value, v
+ if (opts->config_rebase_merges < 0) {
+ opts->config_rebase_merges = 1;
+ parse_rebase_merges_value(opts, value);
-+ }
++ } else
++ opts->rebase_cousins = 0;
+ return 0;
+ }
+
@@ t/t3430-rebase-merges.sh: test_expect_success 'do not rebase cousins unless aske
EOF
'
-+test_expect_success '--rebase-merges="" is deprecated' '
-+ git rebase --rebase-merges="" HEAD^ 2>actual &&
-+ grep deprecated actual
-+'
-+
+test_expect_success 'rebase.rebaseMerges=rebase-cousins is equivalent to --rebase-merges=rebase-cousins' '
+ test_config rebase.rebaseMerges rebase-cousins &&
+ git checkout -b config-rebase-cousins main &&
@@ t/t3430-rebase-merges.sh: test_expect_success 'do not rebase cousins unless aske
+ EOF
+'
+
-+test_expect_success '--rebase-merges=no-rebase-cousins overrides rebase.rebaseMerges=rebase-cousins' '
-+ test_config rebase.rebaseMerges rebase-cousins &&
-+ git checkout -b override-config-rebase-cousins main &&
-+ git rebase --rebase-merges=no-rebase-cousins HEAD^ &&
-+ test_cmp_graph HEAD^.. <<-\EOF
-+ * Merge the topic branch '\''onebranch'\''
-+ |\
-+ | * D
-+ | * G
-+ o | H
-+ |/
-+ o A
-+ EOF
-+'
-+
+test_expect_success '--rebase-merges overrides rebase.rebaseMerges=false' '
+ test_config rebase.rebaseMerges false &&
+ git checkout -b override-config-merges-false E &&
--
2.39.2
next prev parent reply other threads:[~2023-03-12 21:07 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 5:34 [PATCH v4 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-02-23 5:34 ` [PATCH v4 2/3] rebase: stop accepting --rebase-merges="" Alex Henrie
2023-02-24 13:54 ` Johannes Schindelin
2023-02-24 17:20 ` Junio C Hamano
2023-02-24 17:50 ` Alex Henrie
2023-02-24 18:08 ` Junio C Hamano
2023-02-24 18:23 ` Alex Henrie
2023-02-24 18:40 ` Junio C Hamano
2023-02-24 18:55 ` Alex Henrie
2023-02-24 19:13 ` Junio C Hamano
2023-02-24 19:24 ` Alex Henrie
2023-02-24 19:24 ` Phillip Wood
2023-02-24 19:56 ` Alex Henrie
2023-02-23 5:34 ` [PATCH v4 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-02-24 13:53 ` Johannes Schindelin
2023-02-24 17:49 ` Alex Henrie
2023-02-24 14:55 ` Phillip Wood
2023-02-24 17:51 ` Alex Henrie
2023-02-23 17:28 ` [PATCH v4 1/3] rebase: add documentation and test for --no-rebase-merges Junio C Hamano
2023-02-24 13:57 ` Johannes Schindelin
2023-02-24 19:16 ` Junio C Hamano
2023-02-25 18:09 ` Alex Henrie
2023-02-25 18:03 ` [PATCH v5 0/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-02-25 18:03 ` [PATCH v5 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-03-01 23:23 ` Glen Choo
2023-02-25 18:03 ` [PATCH v5 2/3] rebase: deprecate --rebase-merges="" Alex Henrie
2023-03-01 23:46 ` Glen Choo
2023-03-02 10:07 ` Phillip Wood
2023-03-02 18:02 ` Calvin Wan
2023-02-25 18:03 ` [PATCH v5 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-03-01 23:43 ` Glen Choo
2023-03-02 9:37 ` Phillip Wood
2023-03-04 23:24 ` Alex Henrie
2023-03-07 16:23 ` Phillip Wood
2023-03-12 20:57 ` Alex Henrie
2023-03-13 14:20 ` Phillip Wood
2023-03-13 16:12 ` Felipe Contreras
2023-03-13 19:46 ` Junio C Hamano
2023-03-24 14:47 ` About replaying "evil" merges... " Johannes Schindelin
2023-03-02 18:02 ` Calvin Wan
2023-03-04 23:24 ` Alex Henrie
2023-03-01 23:14 ` [PATCH v5 0/3] " Glen Choo
2023-03-02 5:02 ` Alex Henrie
2023-03-02 5:09 ` Alex Henrie
2023-03-05 5:07 ` [PATCH v6 0/3] rebase: document, clean up, and introduce " Alex Henrie
2023-03-05 5:07 ` [PATCH v6 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-03-08 22:25 ` Sergey Organov
2023-03-05 5:07 ` [PATCH v6 2/3] rebase: deprecate --rebase-merges="" Alex Henrie
2023-03-07 14:59 ` Phillip Wood
2023-03-05 5:07 ` [PATCH v6 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-03-07 14:56 ` Phillip Wood
2023-03-07 18:32 ` Junio C Hamano
2023-03-12 21:01 ` Alex Henrie
2023-03-08 0:09 ` Glen Choo
2023-03-08 0:02 ` Glen Choo
2023-03-12 21:03 ` Alex Henrie
2023-03-15 2:52 ` Alex Henrie
2023-03-16 17:32 ` Glen Choo
2023-03-16 18:11 ` Felipe Contreras
2023-03-16 22:46 ` Glen Choo
2023-03-16 23:48 ` Felipe Contreras
2023-03-16 20:27 ` Alex Henrie
2023-03-16 22:39 ` Glen Choo
2023-03-18 5:59 ` Alex Henrie
2023-03-24 15:05 ` Johannes Schindelin
2023-03-25 16:59 ` Sergey Organov
2023-03-05 12:22 ` [PATCH v6 0/3] rebase: document, clean up, and introduce " Sergey Organov
2023-03-05 21:33 ` Alex Henrie
2023-03-05 22:54 ` Sergey Organov
2023-03-06 0:02 ` Alex Henrie
2023-03-06 13:23 ` Sergey Organov
2023-03-06 19:08 ` Junio C Hamano
2023-03-06 17:19 ` Junio C Hamano
2023-03-06 16:24 ` Phillip Wood
2023-03-06 17:36 ` Alex Henrie
2023-03-07 15:07 ` Phillip Wood
2023-03-08 0:13 ` Glen Choo
2023-03-12 21:04 ` Alex Henrie [this message]
2023-03-12 21:04 ` [PATCH v7 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-03-12 21:04 ` [PATCH v7 2/3] rebase: deprecate --rebase-merges="" Alex Henrie
2023-03-12 21:04 ` [PATCH v7 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-03-20 5:59 ` [PATCH v8 0/3] rebase: document, clean up, and introduce " Alex Henrie
2023-03-20 5:59 ` [PATCH v8 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-03-20 5:59 ` [PATCH v8 2/3] rebase: deprecate --rebase-merges="" Alex Henrie
2023-03-20 5:59 ` [PATCH v8 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-03-22 16:54 ` Phillip Wood
2023-03-23 18:45 ` Junio C Hamano
2023-03-24 14:52 ` Phillip Wood
2023-03-25 5:23 ` Alex Henrie
2023-03-25 5:21 ` Alex Henrie
2023-03-26 3:06 ` [PATCH v9 0/3] rebase: document, clean up, and introduce " Alex Henrie
2023-03-26 3:06 ` [PATCH v9 1/3] rebase: add documentation and test for --no-rebase-merges Alex Henrie
2023-03-26 3:06 ` [PATCH v9 2/3] rebase: deprecate --rebase-merges="" Alex Henrie
2023-03-26 3:06 ` [PATCH v9 3/3] rebase: add a config option for --rebase-merges Alex Henrie
2023-03-26 15:12 ` [PATCH v9 0/3] rebase: document, clean up, and introduce " Phillip Wood
2023-03-27 16:33 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230312210456.92364-1-alexhenrie24@gmail.com \
--to=alexhenrie24@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=calvinwan@google.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=sorganov@gmail.com \
--cc=tao@klerks.biz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).