-
Notifications
You must be signed in to change notification settings - Fork 27.9k
Comparing changes
Open a pull request
base repository: git/git
base: 08c36099359e6a5c694f9abb97e630a247bc8dfb
head repository: git/git
compare: 73cc549559398626f33063f64ece9e558e654c95
- 5 commits
- 5 files changed
- 2 contributors
Commits on Feb 24, 2026
-
Merge branch 'jh/alias-i18n' into jh/alias-i18n-fixes
* jh/alias-i18n: completion: fix zsh alias listing for subsection aliases alias: support non-alphanumeric names via subsection syntax alias: prepare for subsection aliases help: use list_aliases() for alias listing
Configuration menu - View commit details
-
Copy full SHA for 874cf0d - Browse repository at this point
Copy the full SHA 874cf0dView commit details
Commits on Feb 26, 2026
-
doc: fix list continuation in alias subsection example
The example showing the equivalence between alias.last and alias.last.command was missing the list continuation marks (+ between the shell session block and the following prose, leaving the paragraph detached from the list item in the rendered output. Signed-off-by: Jonatan Holmgren <jonatan@jontes.page> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Configuration menu - View commit details
-
Copy full SHA for 2e3a987 - Browse repository at this point
Copy the full SHA 2e3a987View commit details -
alias: treat empty subsection [alias ""] as plain [alias]
When git-config stores a key of the form alias..name, it records it under an empty subsection ([alias ""]). The new subsection-aware alias lookup would see a non-NULL but zero-length subsection and fall into the subsection code path, where it required a "command" key and thus silently ignored the entry. Normalize an empty subsection to NULL before any further processing so that entries stored this way continue to work as plain case-insensitive aliases, matching the pre-subsection behaviour. Users who relied on alias..name to create an alias literally named ".name" may want to migrate to subsection syntax, which looks less confusing: [alias ".name"] command = <value> Add tests covering both the empty-subsection compatibility case and the leading-dot alias via the new syntax. Signed-off-by: Jonatan Holmgren <jonatan@jontes.page> Signed-off-by: Junio C Hamano <gitster@pobox.com>Configuration menu - View commit details
-
Copy full SHA for 6589294 - Browse repository at this point
Copy the full SHA 6589294View commit details -
git, help: fix memory leaks in alias listing
The list_aliases() function sets the util pointer of each list item to a heap-allocated copy of the alias command value. Two callers failed to free these util pointers: - list_cmds() in git.c collects a string list with STRING_LIST_INIT_DUP and clears it with string_list_clear(&list, 0), which frees the duplicated strings (strdup_strings=1) but not the util pointers. Pass free_util=1 to free them. - list_cmds_by_config() in help.c calls string_list_sort_u(list, 0) to deduplicate the list before processing completion.commands overrides. When duplicate entries are removed, the util pointer of each discarded item is leaked because free_util=0. Pass free_util=1 to free them. Reported-by: Jacob Keller <jacob.e.keller@intel.com> Signed-off-by: Jonatan Holmgren <jonatan@jontes.page> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Configuration menu - View commit details
-
Copy full SHA for cdef625 - Browse repository at this point
Copy the full SHA cdef625View commit details
Commits on Mar 3, 2026
-
doc: fix list continuation in alias.adoc
Add missing list continuation marks ('+') after code blocks and shell examples so paragraphs render correctly as part of the preceding list item. Signed-off-by: Jonatan Holmgren <jonatan@jontes.page> Signed-off-by: Junio C Hamano <gitster@pobox.com>Configuration menu - View commit details
-
Copy full SHA for 73cc549 - Browse repository at this point
Copy the full SHA 73cc549View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 08c36099359e6a5c694f9abb97e630a247bc8dfb...73cc549559398626f33063f64ece9e558e654c95