From: Phillip Wood <phillip.wood123@gmail.com>
To: Nicolas Guichard via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Eric Sunshine <sunshine@sunshineco.com>,
Nicolas Guichard <nicolas@guichard.eu>
Subject: Re: [PATCH v3 0/3] rebase-merges: try and use branch names for labels
Date: Wed, 9 Oct 2024 15:22:02 +0100 [thread overview]
Message-ID: <c94213e3-f8a6-4f16-9096-f83dbd4e7b7e@gmail.com> (raw)
In-Reply-To: <pull.1784.v3.git.git.1728460700.gitgitgadget@gmail.com>
Hi Nicolas
Thanks for working on this. This version looks good to me
Thanks
Phillip
On 09/10/2024 08:58, Nicolas Guichard via GitGitGadget wrote:
> When interactively rebasing merge commits, the commit message is parsed to
> extract a probably meaningful label name. For instance if the merge commit
> is “Merge branch 'feature0'”, then the rebase script will have thes lines:
>
> label feature0
> merge -C $sha feature0 # “Merge branch 'feature0'
>
>
> This heuristic fails in the case of octopus merges or when the merge commit
> message is actually unrelated to the parent commits.
>
> An example that combines both is:
>
> *---. 967bfa4 (HEAD -> integration) Integration
> |\ \ \
> | | | * 2135be1 (feature2, feat2) Feature 2
> | |_|/
> |/| |
> | | * c88b01a Feature 1
> | |/
> |/|
> | * 75f3139 (feat0) Feature 0
> |/
> * `25c86d0` (main) Initial commit
>
>
> which yields the labels Integration, Integration-2 and Integration-3.
>
> Fix this by using a branch name for each merge commit's parent that is the
> tip of at least one branch, and falling back to a label derived from the
> merge commit message otherwise. In the example above, the labels become
> feat0, Integration and feature2.
>
> Changes since v1:
>
> * moved load_branch_decorations to re-use the decoration_loaded guard and
> avoid pointlessly appending "refs/heads/" to a static string_list, as
> pointed out by Junio C Hamano (thanks!)
> * fixed a leak in load_branch_decorations found by making the filter
> string_lists non-static
>
> Changes since v2:
>
> * style changes (true/false -> 1/0 and // -> /* */)
>
> Nicolas Guichard (3):
> load_branch_decorations: fix memory leak with non-static filters
> rebase-update-refs: extract load_branch_decorations
> rebase-merges: try and use branch names as labels
>
> log-tree.c | 26 +++++++++++++++++++++++++
> log-tree.h | 1 +
> sequencer.c | 36 +++++++++++++++++------------------
> t/t3404-rebase-interactive.sh | 4 ++--
> t/t3430-rebase-merges.sh | 12 ++++++------
> 5 files changed, 53 insertions(+), 26 deletions(-)
>
>
> base-commit: 777489f9e09c8d0dd6b12f9d90de6376330577a2
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1784%2Fnicolas-guichard%2Fuse-branch-names-for-rebase-merges-labels-v3
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1784/nicolas-guichard/use-branch-names-for-rebase-merges-labels-v3
> Pull-Request: https://github.com/git/git/pull/1784
>
> Range-diff vs v2:
>
> 1: 6250a7f6d6c ! 1: e030ddd91f3 load_branch_decorations: fix memory leak with non-static filters
> @@ log-tree.c: void load_ref_decorations(struct decoration_filter *filter, int flag
> normalize_glob_ref(item, NULL, item->string);
> }
> +
> -+ // normalize_glob_ref duplicates the strings
> -+ filter->exclude_ref_pattern->strdup_strings = true;
> -+ filter->include_ref_pattern->strdup_strings = true;
> -+ filter->exclude_ref_config_pattern->strdup_strings = true;
> ++ /* normalize_glob_ref duplicates the strings */
> ++ filter->exclude_ref_pattern->strdup_strings = 1;
> ++ filter->include_ref_pattern->strdup_strings = 1;
> ++ filter->exclude_ref_config_pattern->strdup_strings = 1;
> }
> decoration_loaded = 1;
> decoration_flags = flags;
> 2: 167418d10d1 ! 2: 1dad6096eb7 rebase-update-refs: extract load_branch_decorations
> @@ log-tree.c: void load_ref_decorations(struct decoration_filter *filter, int flag
> + string_list_append(&decorate_refs_include, "refs/heads/");
> + load_ref_decorations(&decoration_filter, 0);
> +
> -+ string_list_clear(&decorate_refs_exclude, false);
> -+ string_list_clear(&decorate_refs_exclude_config, false);
> -+ string_list_clear(&decorate_refs_include, false);
> ++ string_list_clear(&decorate_refs_exclude, 0);
> ++ string_list_clear(&decorate_refs_exclude_config, 0);
> ++ string_list_clear(&decorate_refs_include, 0);
> + }
> +}
> +
> 3: dfa1f0a7648 = 3: 19d8253da07 rebase-merges: try and use branch names as labels
>
prev parent reply other threads:[~2024-10-09 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 18:37 [PATCH 0/2] rebase-merges: try and use branch names for labels Nicolas Guichard via GitGitGadget
2024-09-21 18:37 ` [PATCH 1/2] sequencer.c: extract load_branch_decorations Nicolas Guichard via GitGitGadget
2024-09-23 19:32 ` Junio C Hamano
2024-09-21 18:38 ` [PATCH 2/2] rebase-merges: try and use branch names as labels Nicolas Guichard via GitGitGadget
2024-09-23 19:38 ` Junio C Hamano
2024-10-04 23:22 ` [PATCH v2 0/3] rebase-merges: try and use branch names for labels Nicolas Guichard via GitGitGadget
2024-10-04 23:22 ` [PATCH v2 1/3] load_branch_decorations: fix memory leak with non-static filters Nicolas Guichard via GitGitGadget
2024-10-05 3:43 ` Eric Sunshine
2024-10-04 23:22 ` [PATCH v2 2/3] rebase-update-refs: extract load_branch_decorations Nicolas Guichard via GitGitGadget
2024-10-05 3:44 ` Eric Sunshine
2024-10-04 23:22 ` [PATCH v2 3/3] rebase-merges: try and use branch names as labels Nicolas Guichard via GitGitGadget
2024-10-09 7:58 ` [PATCH v3 0/3] rebase-merges: try and use branch names for labels Nicolas Guichard via GitGitGadget
2024-10-09 7:58 ` [PATCH v3 1/3] load_branch_decorations: fix memory leak with non-static filters Nicolas Guichard via GitGitGadget
2024-10-09 7:58 ` [PATCH v3 2/3] rebase-update-refs: extract load_branch_decorations Nicolas Guichard via GitGitGadget
2024-10-09 7:58 ` [PATCH v3 3/3] rebase-merges: try and use branch names as labels Nicolas Guichard via GitGitGadget
2024-10-09 14:21 ` Phillip Wood
2024-10-09 17:57 ` Junio C Hamano
2024-10-09 14:22 ` Phillip Wood [this message]
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=c94213e3-f8a6-4f16-9096-f83dbd4e7b7e@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=nicolas@guichard.eu \
--cc=phillip.wood@dunelm.org.uk \
--cc=sunshine@sunshineco.com \
/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 NNTP newsgroup(s).