Skip to content

Rebase shears/seen: 1 conflict(s) (0 skipped, 1 resolved) (#24113731296)#100

Open
gitforwindowshelper[bot] wants to merge 281 commits intobase/shears/seen-24113731296from
shears/seen-24113731296
Open

Rebase shears/seen: 1 conflict(s) (0 skipped, 1 resolved) (#24113731296)#100
gitforwindowshelper[bot] wants to merge 281 commits intobase/shears/seen-24113731296from
shears/seen-24113731296

Conversation

@gitforwindowshelper
Copy link
Copy Markdown

Workflow run

Rebase Summary: seen

From: 695ccca8de (Detect number of cores better on multi-socket systems (git-for-windows#6108), 2026-04-06) (a53c8e49ab..695ccca8de)

Resolved: 0ca8b9d (Winansi: Drop pre-Vista workaround (git-for-windows#6109), 2026-04-06)

All conflicts resolved by keeping HEAD versions; the winansi commit (44760f1) only modifies compat/winansi.c and doesn't touch any conflicting files

Range-diff
  • 1: 0ca8b9d ! 1: f08c06a Winansi: Drop pre-Vista workaround (Winansi: Drop pre-Vista workaround git#6109)

    @@ Commit message
         1.21 and newer only support Windows 10 and newer. So this might become a
         problem at any point.
     
    - ## Documentation/config.adoc ##
    -@@ Documentation/config.adoc: include::config/sequencer.adoc[]
    - 
    - include::config/showbranch.adoc[]
    - 
    -+include::config/sideband.adoc[]
    -+
    - include::config/sparse.adoc[]
    - 
    - include::config/splitindex.adoc[]
    -
    - ## Documentation/config/sideband.adoc (new) ##
    + ## Documentation/config/sideband.adoc ##
    + remerge CONFLICT (add/add): Merge conflict in Documentation/config/sideband.adoc
    + index fbe4b20235..ddba93393c 100644
    + --- Documentation/config/sideband.adoc
    + +++ Documentation/config/sideband.adoc
     @@
    -+sideband.allowControlCharacters::
    -+	By default, control characters that are delivered via the sideband
    -+	are masked, except ANSI color sequences. This prevents potentially
    -+	unwanted ANSI escape sequences from being sent to the terminal. Use
    -+	this config setting to override this behavior:
    -++
    -+--
    -+	color::
    -+		Allow ANSI color sequences, line feeds and horizontal tabs,
    -+		but mask all other control characters. This is the default.
    -+	false::
    -+		Mask all control characters other than line feeds and
    -+		horizontal tabs.
    -+	true::
    -+		Allow all control characters to be sent to the terminal.
    -+--
    + sideband.allowControlCharacters::
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + ifdef::with-breaking-changes[]
    + 	By default, control characters that are delivered via the sideband
    + 	are masked, except ANSI color sequences. This prevents potentially
    +@@ Documentation/config/sideband.adoc: endif::with-breaking-changes[]
    + sideband.<url>.*::
    + 	Apply the `sideband.*` option selectively to specific URLs. The
    + 	same URL matching logic applies as for `http.<url>.*` settings.
    +-=======
    +-	By default, control characters that are delivered via the sideband
    +-	are masked, except ANSI color sequences. This prevents potentially
    +-	unwanted ANSI escape sequences from being sent to the terminal. Use
    +-	this config setting to override this behavior:
    +-+
    +---
    +-	color::
    +-		Allow ANSI color sequences, line feeds and horizontal tabs,
    +-		but mask all other control characters. This is the default.
    +-	false::
    +-		Mask all control characters other than line feeds and
    +-		horizontal tabs.
    +-	true::
    +-		Allow all control characters to be sent to the terminal.
    +---
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
     
    - ## Documentation/git-svn.adoc ##
    -@@ Documentation/git-svn.adoc: SYNOPSIS
    - --------
    - [verse]
    - 'git svn' <command> [<options>] [<arguments>]
    -+(UNSUPPORTED!)
    - 
    - DESCRIPTION
    - -----------
    + ## builtin/reset.c ##
    + remerge CONFLICT (content): Merge conflict in builtin/reset.c
    + index 3bd7d56684..8e3c8509d7 100644
    + --- builtin/reset.c
    + +++ builtin/reset.c
    +@@ builtin/reset.c: int cmd_reset(int argc,
    + 	struct object_id oid;
    + 	struct pathspec pathspec;
    + 	int intent_to_add = 0;
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	struct interactive_options interactive_opts = INTERACTIVE_OPTIONS_INIT;
    +-=======
    +-	struct add_p_opt add_p_opt = ADD_P_OPT_INIT;
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 	int nul_term_line = 0, read_from_stdin = 0;
    + 	const struct option options[] = {
    + 		OPT__QUIET(&quiet, N_("be quiet, only report errors")),
     
    - ## git-svn.perl ##
    -@@ git-svn.perl: sub term_init {
    - 			: new Term::ReadLine 'git-svn';
    - }
    + ## git-curl-compat.h ##
    + remerge CONFLICT (content): Merge conflict in git-curl-compat.h
    + index cd9ec49139..5c8ceb076a 100644
    + --- git-curl-compat.h
    + +++ git-curl-compat.h
    +@@
    + #endif
      
    -+sub deprecated_warning {
    -+    my @lines = @_;
    -+    if (-t STDERR) {
    -+        @lines = map { "\e[33m$_\e[0m" } @lines;
    -+    }
    -+    warn join("\n", @lines), "\n";
    -+}
    -+
    -+deprecated_warning(
    -+	"WARNING: \`git svn\` is no longer supported by the Git for Windows project.",
    -+	"See https://github.com/git-for-windows/git/issues/5405 for details."
    -+);
    -+
    - my $cmd;
    - for (my $i = 0; $i < @ARGV; $i++) {
    - 	if (defined $cmd{$ARGV[$i]}) {
    + /**
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    +  * CURLINFO_RETRY_AFTER was added in 7.66.0, released in September 2019.
    +  * It allows curl to automatically parse Retry-After headers.
    +  */
    +@@
    + #endif
    + 
    + /**
    +-=======
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    +  * CURLSSLOPT_AUTO_CLIENT_CERT was added in 7.77.0, released in May
    +  * 2021.
    +  */
     
      ## http.c ##
    -@@ http.c: static long http_retry_after = 0;
    + remerge CONFLICT (content): Merge conflict in http.c
    + index 6d557dd0e5..54cbf8ed7a 100644
    + --- http.c
    + +++ http.c
    +@@ http.c: static long http_schannel_check_revoke_mode =
    + 	CURLSSLOPT_NO_REVOKE;
    + #endif
    + 
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + static long http_retry_after = 0;
      static long http_max_retries = 0;
      static long http_max_retry_time = 300;
      
    -+
    +-=======
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
      /*
       * With the backend being set to `schannel`, setting sslCAinfo would override
       * the Certificate Store in cURL v7.60.0 and later, which is not what we want
     
    + ## refs/reftable-backend.c ##
    + remerge CONFLICT (content): Merge conflict in refs/reftable-backend.c
    + index ebb7d4c9b1..0ad77482ff 100644
    + --- refs/reftable-backend.c
    + +++ refs/reftable-backend.c
    +@@ refs/reftable-backend.c: static struct ref_store *reftable_be_init(struct repository *repo,
    + 	umask(mask);
    + 
    + 	reftable_set_alloc(malloc, realloc, free);
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 
    + 	refs_compute_filesystem_location(gitdir, payload, &is_worktree, &refdir,
    + 					 &ref_common_dir);
    + 
    + 	base_ref_store_init(&refs->base, repo, refdir.buf, &refs_be_reftable);
    +-=======
    +-	base_ref_store_init(&refs->base, repo, gitdir, &refs_be_reftable);
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 	strmap_init(&refs->worktree_backends);
    + 	refs->store_flags = store_flags;
    + 	refs->log_all_ref_updates = repo_settings_get_log_all_ref_updates(repo);
    +
      ## sideband.c ##
    + remerge CONFLICT (content): Merge conflict in sideband.c
    + index e853e7fe5c..26e5bbd4b5 100644
    + --- sideband.c
    + +++ sideband.c
     @@ sideband.c: static struct keyword_entry keywords[] = {
    - 	{ "error",	GIT_COLOR_BOLD_RED },
      };
      
    -+static enum {
    -+	ALLOW_NO_CONTROL_CHARACTERS = 0,
    -+	ALLOW_ALL_CONTROL_CHARACTERS = 1,
    -+	ALLOW_ANSI_COLOR_SEQUENCES = 2
    -+} allow_control_characters = ALLOW_ANSI_COLOR_SEQUENCES;
    -+
    + static enum {
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	ALLOW_CONTROL_SEQUENCES_UNSET = -1,
    + 	ALLOW_NO_CONTROL_CHARACTERS   = 0,
    + 	ALLOW_ANSI_COLOR_SEQUENCES    = 1<<0,
    +@@ sideband.c: void sideband_apply_url_config(const char *url)
    + 	string_list_clear(&config.vars, 1);
    + 	urlmatch_config_release(&config);
    + }
    +-=======
    +-	ALLOW_NO_CONTROL_CHARACTERS = 0,
    +-	ALLOW_ALL_CONTROL_CHARACTERS = 1,
    +-	ALLOW_ANSI_COLOR_SEQUENCES = 2
    +-} allow_control_characters = ALLOW_ANSI_COLOR_SEQUENCES;
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 
      /* Returns a color setting (GIT_COLOR_NEVER, etc). */
      static enum git_colorbool use_sideband_colors(void)
    - {
     @@ sideband.c: static enum git_colorbool use_sideband_colors(void)
      	if (use_sideband_colors_cached != GIT_COLOR_UNKNOWN)
      		return use_sideband_colors_cached;
      
    -+	switch (repo_config_get_maybe_bool(the_repository, "sideband.allowcontrolcharacters", &i)) {
    -+	case 0: /* Boolean value */
    -+		allow_control_characters = i ? ALLOW_ALL_CONTROL_CHARACTERS :
    -+			ALLOW_NO_CONTROL_CHARACTERS;
    -+		break;
    -+	case -1: /* non-Boolean value */
    -+		if (repo_config_get_string_tmp(the_repository, "sideband.allowcontrolcharacters",
    -+					      &value))
    -+			; /* huh? `get_maybe_bool()` returned -1 */
    -+		else if (!strcmp(value, "color"))
    -+			allow_control_characters = ALLOW_ANSI_COLOR_SEQUENCES;
    -+		else
    -+			warning(_("unrecognized value for `sideband."
    -+				  "allowControlCharacters`: '%s'"), value);
    -+		break;
    -+	default:
    -+		break; /* not configured */
    -+	}
    -+
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	if (allow_control_characters == ALLOW_CONTROL_SEQUENCES_UNSET) {
    + 		if (!repo_config_get_value(the_repository, "sideband.allowcontrolcharacters", &value))
    + 			sideband_allow_control_characters_config("sideband.allowcontrolcharacters", value);
    + 
    + 		if (allow_control_characters == ALLOW_CONTROL_SEQUENCES_UNSET)
    + 			allow_control_characters = ALLOW_DEFAULT_ANSI_SEQUENCES;
    +-=======
    +-	switch (repo_config_get_maybe_bool(the_repository, "sideband.allowcontrolcharacters", &i)) {
    +-	case 0: /* Boolean value */
    +-		allow_control_characters = i ? ALLOW_ALL_CONTROL_CHARACTERS :
    +-			ALLOW_NO_CONTROL_CHARACTERS;
    +-		break;
    +-	case -1: /* non-Boolean value */
    +-		if (repo_config_get_string_tmp(the_repository, "sideband.allowcontrolcharacters",
    +-					      &value))
    +-			; /* huh? `get_maybe_bool()` returned -1 */
    +-		else if (!strcmp(value, "color"))
    +-			allow_control_characters = ALLOW_ANSI_COLOR_SEQUENCES;
    +-		else
    +-			warning(_("unrecognized value for `sideband."
    +-				  "allowControlCharacters`: '%s'"), value);
    +-		break;
    +-	default:
    +-		break; /* not configured */
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 	}
    + 
      	if (!repo_config_get_string_tmp(the_repository, key, &value))
    - 		use_sideband_colors_cached = git_config_colorbool(key, value);
    - 	else if (!repo_config_get_string_tmp(the_repository, "color.ui", &value))
     @@ sideband.c: void list_config_color_sideband_slots(struct string_list *list, const char *pref
      		list_config_item(list, prefix, keywords[i].keyword);
      }
      
    -+static int handle_ansi_color_sequence(struct strbuf *dest, const char *src, int n)
    -+{
    -+	int i;
    -+
    -+	/*
    -+	 * Valid ANSI color sequences are of the form
    -+	 *
    -+	 * ESC [ [<n> [; <n>]*] m
    -+	 */
    -+
    -+	if (allow_control_characters != ALLOW_ANSI_COLOR_SEQUENCES ||
    -+	    n < 3 || src[0] != '\x1b' || src[1] != '[')
    -+		return 0;
    -+
    -+	for (i = 2; i < n; i++) {
    -+		if (src[i] == 'm') {
    -+			strbuf_add(dest, src, i + 1);
    -+			return i;
    -+		}
    -+		if (!isdigit(src[i]) && src[i] != ';')
    -+			break;
    -+	}
    -+
    -+	return 0;
    -+}
    -+
    -+static void strbuf_add_sanitized(struct strbuf *dest, const char *src, int n)
    -+{
    -+	int i;
    -+
    -+	if (allow_control_characters == ALLOW_ALL_CONTROL_CHARACTERS) {
    -+		strbuf_add(dest, src, n);
    -+		return;
    -+	}
    -+
    -+	strbuf_grow(dest, n);
    -+	for (; n && *src; src++, n--) {
    -+		if (!iscntrl(*src) || *src == '\t' || *src == '\n')
    -+			strbuf_addch(dest, *src);
    -+		else if ((i = handle_ansi_color_sequence(dest, src, n))) {
    -+			src += i;
    -+			n -= i;
    -+		} else {
    -+			strbuf_addch(dest, '^');
    -+			strbuf_addch(dest, 0x40 + *src);
    -+		}
    -+	}
    -+}
    -+
    - /*
    -  * Optionally highlight one keyword in remote output if it appears at the start
    -  * of the line. This should be called for a single line only, which is
    -@@ sideband.c: static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + static int handle_ansi_sequence(struct strbuf *dest, const char *src, int n)
    +-=======
    +-static int handle_ansi_color_sequence(struct strbuf *dest, const char *src, int n)
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + {
    + 	int i;
    + 
    +@@ sideband.c: static int handle_ansi_color_sequence(struct strbuf *dest, const char *src, int
    + 	 * Valid ANSI color sequences are of the form
    + 	 *
    + 	 * ESC [ [<n> [; <n>]*] m
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	 *
    + 	 * These are part of the Select Graphic Rendition sequences which
    + 	 * contain more than just color sequences, for more details see
    +@@ sideband.c: static int handle_ansi_color_sequence(struct strbuf *dest, const char *src, int
    + 		     strchr("ABCDEFGHf", src[i])) ||
    + 		    ((allow_control_characters & ALLOW_ANSI_ERASE) &&
    + 		     strchr("JKMPX", src[i]))) {
    +-=======
    +-	 */
    +-
    +-	if (allow_control_characters != ALLOW_ANSI_COLOR_SEQUENCES ||
    +-	    n < 3 || src[0] != '\x1b' || src[1] != '[')
    +-		return 0;
    +-
    +-	for (i = 2; i < n; i++) {
    +-		if (src[i] == 'm') {
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 			strbuf_add(dest, src, i + 1);
    + 			return i;
    + 		}
    +@@ sideband.c: static void strbuf_add_sanitized(struct strbuf *dest, const char *src, int n)
    + {
      	int i;
      
    - 	if (!want_color_stderr(use_sideband_colors())) {
    --		strbuf_add(dest, src, n);
    -+		strbuf_add_sanitized(dest, src, n);
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	if ((allow_control_characters & ALLOW_ALL_CONTROL_CHARACTERS)) {
    +-=======
    +-	if (allow_control_characters == ALLOW_ALL_CONTROL_CHARACTERS) {
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 		strbuf_add(dest, src, n);
      		return;
      	}
      
    -@@ sideband.c: static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
    + 	strbuf_grow(dest, n);
    + 	for (; n && *src; src++, n--) {
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 		if (!iscntrl(*src) || *src == '\t' || *src == '\n') {
    + 			strbuf_addch(dest, *src);
    + 		} else if (allow_control_characters != ALLOW_NO_CONTROL_CHARACTERS &&
    + 			   (i = handle_ansi_sequence(dest, src, n))) {
    +-=======
    +-		if (!iscntrl(*src) || *src == '\t' || *src == '\n')
    +-			strbuf_addch(dest, *src);
    +-		else if ((i = handle_ansi_color_sequence(dest, src, n))) {
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 			src += i;
    + 			n -= i;
    + 		} else {
    + 			strbuf_addch(dest, '^');
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 			strbuf_addch(dest, *src == 0x7f ? '?' : 0x40 + *src);
    +-=======
    +-			strbuf_addch(dest, 0x40 + *src);
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
      		}
      	}
    - 
    --	strbuf_add(dest, src, n);
    -+	strbuf_add_sanitized(dest, src, n);
      }
    - 
    - 
    +
    + ## t/meson.build ##
    + remerge CONFLICT (content): Merge conflict in t/meson.build
    + index 65bec885dc..25272d7ae4 100644
    + --- t/meson.build
    + +++ t/meson.build
    +@@ t/meson.build: integration_tests = [
    +   't7422-submodule-output.sh',
    +   't7423-submodule-symlinks.sh',
    +   't7424-submodule-mixed-ref-formats.sh',
    +-<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    +   't7425-submodule-gitdir-path-extension.sh',
    +   't7426-submodule-get-default-remote.sh',
    +-=======
    +->>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    +   't7429-submodule-long-path.sh',
    +   't7450-bad-git-dotfiles.sh',
    +   't7500-commit-template-squash-signoff.sh',
     
      ## t/t5409-colorize-remote-messages.sh ##
    + remerge CONFLICT (content): Merge conflict in t/t5409-colorize-remote-messages.sh
    + index 38df45751f..07cbc62736 100755
    + --- t/t5409-colorize-remote-messages.sh
    + +++ t/t5409-colorize-remote-messages.sh
     @@ t/t5409-colorize-remote-messages.sh: test_expect_success 'fallback to color.ui' '
      	grep "<BOLD;RED>error<RESET>: error" decoded
      '
      
    -+test_expect_success 'disallow (color) control sequences in sideband' '
    -+	write_script .git/color-me-surprised <<-\EOF &&
    -+	printf "error: Have you \\033[31mread\\033[m this?\\a\\n" >&2
    -+	exec "$@"
    -+	EOF
    -+	test_config_global uploadPack.packObjectshook ./color-me-surprised &&
    -+	test_commit need-at-least-one-commit &&
    -+
    -+	git clone --no-local . throw-away 2>stderr &&
    -+	test_decode_color <stderr >decoded &&
    -+	test_grep RED decoded &&
    -+	test_grep "\\^G" stderr &&
    -+	tr -dc "\\007" <stderr >actual &&
    -+	test_must_be_empty actual &&
    -+
    -+	rm -rf throw-away &&
    -+	git -c sideband.allowControlCharacters=false \
    -+		clone --no-local . throw-away 2>stderr &&
    -+	test_decode_color <stderr >decoded &&
    -+	test_grep ! RED decoded &&
    -+	test_grep "\\^G" stderr &&
    -+
    -+	rm -rf throw-away &&
    -+	git -c sideband.allowControlCharacters clone --no-local . throw-away 2>stderr &&
    -+	test_decode_color <stderr >decoded &&
    -+	test_grep RED decoded &&
    -+	tr -dc "\\007" <stderr >actual &&
    -+	test_file_not_empty actual
    -+'
    -+
    - test_done
    -
    - ## t/t9108-git-svn-glob.sh ##
    -@@ t/t9108-git-svn-glob.sh: test_expect_success 'test disallow multi-globs' '
    - 		svn_cmd commit -m "try to try"
    - 	) &&
    - 	test_must_fail git svn fetch three 2> stderr.three &&
    --	test_cmp expect.three stderr.three
    -+	sed "/^WARNING.*no.* supported/{N;d}" <stderr.three >stderr.three.clean &&
    -+	test_cmp expect.three stderr.three.clean
    - 	'
    +-<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + if test_have_prereq WITH_BREAKING_CHANGES
    + then
    + 	TURN_ON_SANITIZING=already.turned=on
    +@@ t/t5409-colorize-remote-messages.sh: else
    + 	TURN_ON_SANITIZING=sideband.allowControlCharacters=color
    + fi
      
    - test_done
    -
    - ## t/t9109-git-svn-multi-glob.sh ##
    -@@ t/t9109-git-svn-multi-glob.sh: test_expect_success 'test disallow multiple globs' '
    - 		svn_cmd commit -m "try to try"
    - 	) &&
    - 	test_must_fail git svn fetch three 2> stderr.three &&
    --	test_cmp expect.three stderr.three
    -+	sed "/^WARNING.*no.* supported/{N;d}" <stderr.three >stderr.three.clean &&
    -+	test_cmp expect.three stderr.three.clean
    - 	'
    +-================================
    +->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + test_expect_success 'disallow (color) control sequences in sideband' '
    + 	write_script .git/color-me-surprised <<-\EOF &&
    + 	printf "error: Have you \\033[31mread\\033[m this?\\a\\n" >&2
    + 	exec "$@"
    + 	EOF
    +-<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + 	test_config_global uploadPack.packObjectsHook ./color-me-surprised &&
    + 	test_commit need-at-least-one-commit &&
      
    - test_done
    -
    - ## t/t9168-git-svn-partially-globbed-names.sh ##
    -@@ t/t9168-git-svn-partially-globbed-names.sh: test_expect_success 'test disallow prefixed multi-globs' '
    - 		svn_cmd commit -m "try to try"
    - 	) &&
    - 	test_must_fail git svn fetch four 2>stderr.four &&
    --	test_cmp expect.four stderr.four &&
    -+	sed "/^WARNING.*no.* supported/{N;d}" <stderr.four >stderr.four.clean &&
    -+	test_cmp expect.four stderr.four.clean &&
    - 	git config --unset svn-remote.four.branches &&
    - 	git config --unset svn-remote.four.tags
    - 	'
    -@@ t/t9168-git-svn-partially-globbed-names.sh: test_expect_success 'test disallow multiple asterisks in one word' '
    - 		svn_cmd commit -m "try to try"
    - 	) &&
    - 	test_must_fail git svn fetch six 2>stderr.six &&
    --	test_cmp expect.six stderr.six
    -+	sed "/^WARNING.*no.* supported/{N;d}" <stderr.six >stderr.six.clean &&
    -+	test_cmp expect.six stderr.six.clean
    - 	'
    + 	git -c $TURN_ON_SANITIZING clone --no-local . throw-away 2>stderr &&
    +-================================
    +-	test_config_global uploadPack.packObjectshook ./color-me-surprised &&
    +-	test_commit need-at-least-one-commit &&
    +-
    +-	git clone --no-local . throw-away 2>stderr &&
    +->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
    + 	test_decode_color <stderr >decoded &&
    + 	test_grep RED decoded &&
    + 	test_grep "\\^G" stderr &&
    +@@ t/t5409-colorize-remote-messages.sh: test_expect_success 'disallow (color) control sequences in sideband' '
    + 	test_file_not_empty actual
    + '
    + 
    +-<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 0cd8e9a8dd (Merge 'readme' into HEAD)
    + test_decode_csi() {
    + 	awk '{
    + 		while (match($0, /\033/) != 0) {
    +@@ t/t5409-colorize-remote-messages.sh: test_expect_success 'allow all control sequences for a specific URL' '
    + 	test_grep ! "\\^\\[\\[K" decoded
    + '
      
    +-================================
    +->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 44760f1bb6 (compat/winansi: drop pre-Vista workaround)
      test_done

To: 35316ae542 (Detect number of cores better on multi-socket systems (git-for-windows#6108), 2026-04-06) (ecedea27a2..35316ae542)

Statistics

Metric Count
Total conflicts 1
Skipped (upstreamed) 0
Resolved surgically 1
Range-diff (click to expand)

bmueller84 and others added 30 commits April 8, 2026 02:04
In 1e64d18 (mingw: do resolve symlinks in `getcwd()`) a problem was
introduced that causes git for Windows to stop working with certain
mapped network drives (in particular, drives that are mapped to
locations with long path names). Error message was "fatal: Unable to
read current working directory: No such file or directory". Present
change fixes this issue as discussed in
git-for-windows#2480

Signed-off-by: Bjoern Mueller <bjoernm@gmx.de>
Update clink.pl to link with either libcurl.lib or libcurl-d.lib
depending on whether DEBUG=1 is set.

Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
There is a Win32 API function to resolve symbolic links, and we can use
that instead of resolving them manually. Even better, this function also
resolves NTFS junction points (which are somewhat similar to bind
mounts).

This fixes git-for-windows#2481.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The native Windows HTTPS backend is based on Secure Channel which lets
the caller decide how to handle revocation checking problems caused by
missing information in the certificate or offline CRL distribution
points.

Unfortunately, cURL chose to handle these problems differently than
OpenSSL by default: while OpenSSL happily ignores those problems
(essentially saying "¯\_(ツ)_/¯"), the Secure Channel backend will error
out instead.

As a remedy, the "no revoke" mode was introduced, which turns off
revocation checking altogether. This is a bit heavy-handed. We support
this via the `http.schannelCheckRevoke` setting.

In curl/curl#4981, we contributed an opt-in
"best effort" strategy that emulates what OpenSSL seems to do.

In Git for Windows, we actually want this to be the default. This patch
makes it so, introducing it as a new value for the
`http.schannelCheckRevoke" setting, which now becmes a tristate: it
accepts the values "false", "true" or "best-effort" (defaulting to the
last one).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The convention in Git project's shell scripts is to have white-space
_before_, but not _after_ the `>` (or `<`).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This change enhances `git commit --cleanup=scissors` by detecting
scissors lines ending in either LF (UNIX-style) or CR/LF (DOS-style).

Regression tests are included to specifically test for trailing
comments after a CR/LF-terminated scissors line.

Signed-off-by: Luke Bonanomi <lbonanomi@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
For some reason, this test case was indented with 4 spaces instead of 1
horizontal tab. The other test cases in the same test script are fine.

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
As of Git v2.28.0, the diff for files staged via `git add -N` marks them
as new files. Git GUI was ill-prepared for that, and this patch teaches
Git GUI about them.

Please note that this will not even fix things with v2.28.0, as the
`rp/apply-cached-with-i-t-a` patches are required on Git's side, too.

This fixes git-for-windows#2779

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Pratyush Yadav <me@yadavpratyush.com>
The vcpkg downloads may not succeed. Warn careful readers of the time out.

A simple retry will usually resolve the issue.

Signed-off-by: Philip Oakley <philipoakley@iee.email>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Dennis Ameling <dennis@dennisameling.com>
Git's regular Makefile mentions that HOST_CPU should be defined when cross-compiling Git: https://github.com/git-for-windows/git/blob/37796bca76ef4180c39ee508ca3e42c0777ba444/Makefile#L438-L439

This is then used to set the GIT_HOST_CPU variable when compiling Git: https://github.com/git-for-windows/git/blob/37796bca76ef4180c39ee508ca3e42c0777ba444/Makefile#L1337-L1341

Then, when the user runs `git version --build-options`, it returns that value: https://github.com/git-for-windows/git/blob/37796bca76ef4180c39ee508ca3e42c0777ba444/help.c#L658

This commit adds the same functionality to the CMake configuration. Users can now set -DHOST_CPU= to set the target architecture.

Signed-off-by: Dennis Ameling <dennis@dennisameling.com>
These fixes have been sent to the Git mailing list but have not been
picked up by the Git project yet.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
As reported in newren/git-filter-repo#225, it
looks like 99 bytes is not really sufficient to represent e.g. the full
path to Python when installed via Windows Store (and this path is used
in the hasb bang line when installing scripts via `pip`).

Let's increase it to what is probably the maximum sensible path size:
MAX_PATH. This makes `parse_interpreter()` in line with what
`lookup_prog()` handles.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Vilius Šumskas <vilius@sumskas.eu>
We used to have that `make vcxproj` hack, but a hack it is. In the
meantime, we have a much cleaner solution: using CMake, either
explicitly, or even more conveniently via Visual Studio's built-in CMake
support (simply open Git's top-level directory via File>Open>Folder...).

Let's let the `README` reflect this.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This adds support for a new http.sslAutoClientCert config value.

In cURL 7.77 or later the schannel backend does not automatically send
client certificates from the Windows Certificate Store anymore.

This config value is only used if http.sslBackend is set to "schannel",
and can be used to opt in to the old behavior and force cURL to send
client certificates.

This fixes git-for-windows#3292

Signed-off-by: Pascal Muller <pascalmuller@gmail.com>
Because `git subtree` (unlike most other `contrib` modules) is included as
part of the standard release of Git for Windows, its stability should be
verified as consistently as it is for the rest of git. By including the
`git subtree` tests in the CI workflow, these tests are as much of a gate to
merging and indicator of stability as the standard test suite.

Signed-off-by: Victoria Dye <vdye@github.com>
Ensure key CMake option values are part of the CMake output to
facilitate user support when tool updates impact the wider CMake
actions, particularly ongoing 'improvements' in Visual Studio.

These CMake displays perform the same function as the build-options.txt
provided in the main Git for Windows. CMake is already chatty.
The setting of CMAKE_EXPORT_COMPILE_COMMANDS is also reported.

Include the environment's CMAKE_EXPORT_COMPILE_COMMANDS value which
may have been propogated to CMake's internal value.

Testing the CMAKE_EXPORT_COMPILE_COMMANDS processing can be difficult
in the Visual Studio environment, as it may be cached in many places.
The 'environment' may include the OS, the user shell, CMake's
own environment, along with the Visual Studio presets and caches.

See previous commit for arefacts that need removing for a clean test.

Signed-off-by: Philip Oakley <philipoakley@iee.email>
This is no longer true in general, not with supporting Clang out of the
box.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This option was added in fa93bb2 (MinGW: Fix stat definitions to
work with MinGW runtime version 4.0, 2013-09-11), i.e. a _long_ time
ago. So long, in fact, that it still targeted MinGW. But we switched to
mingw-w64 in 2015, which seems not to share the problem, and therefore
does not require a fix.

Even worse: This flag is incompatible with UCRT64, which we are about to
support by way of upstreaming `mingw-w64-git` to the MSYS2 project, see
msys2/MINGW-packages#26470 for details.

So let's send that option into its well-deserved retirement.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Merge this early to resolve merge conflicts early.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
That option only matters there, and is in fact only really understood in
those builds; UCRT64 versions of GCC, for example, do not know what to
do with that option.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
When building with `make MSVC=1 DEBUG=1`, link to `libexpatd.lib`
rather than `libexpat.lib`.

It appears that the `vcpkg` package for "libexpat" has changed and now
creates `libexpatd.lib` for debug mode builds.  Previously, both debug
and release builds created a ".lib" with the same basename.

Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
In bf2d5d8 (Don't let ld strip relocations, 2016-01-16) (picked from
git-for-windows@6a237925bf10),
Git for Windows introduced the `-Wl,-pic-executable` flag, specifying
the exact entry point via `-e`. This required discerning between i686
and x86_64 code because the former required the symbol to be prefixed
with an underscore, the latter did not.

As per https://sourceware.org/bugzilla/show_bug.cgi?id=10865, the
specified symbols are already the default, though.

So let's drop the overly-specific definition.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
MSYS2 already defines a couple of helpful environment variables, and we
can use those to infer the installation location as well as the CPU. No
need for hard-coding ;-)

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Create a wrapper for the Windows Resource Compiler (RC.EXE)
for use by the MSVC=1 builds. This is similar to the CL.EXE
and LIB.EXE wrappers used for the MSVC=1 builds.

Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
Continue walking the code path for the >4GB `hash-object --literally`
test to the hash algorithm step for LLP64 systems.

This patch lets the SHA1DC code use `size_t`, making it compatible with
LLP64 data models (as used e.g. by Windows).

The interested reader of this patch will note that we adjust the
signature of the `git_SHA1DCUpdate()` function without updating _any_
call site. This certainly puzzled at least one reviewer already, so here
is an explanation:

This function is never called directly, but always via the macro
`platform_SHA1_Update`, which is usually called via the macro
`git_SHA1_Update`. However, we never call `git_SHA1_Update()` directly
in `struct git_hash_algo`. Instead, we call `git_hash_sha1_update()`,
which is defined thusly:

    static void git_hash_sha1_update(git_hash_ctx *ctx,
                                     const void *data, size_t len)
    {
        git_SHA1_Update(&ctx->sha1, data, len);
    }

i.e. it contains an implicit downcast from `size_t` to `unsigned long`
(before this here patch). With this patch, there is no downcast anymore.

With this patch, finally, the t1007-hash-object.sh "files over 4GB hash
literally" test case is fixed.

Signed-off-by: Philip Oakley <philipoakley@iee.email>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The tell-tale is the presence of the `MSYSTEM` value while compiling, of
course. In that case, we want to ensure that `MSYSTEM` is set when
running `git.exe`, and also enable the magic MSYS2 tty detection.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Teach MSVC=1 builds to depend on the `git.rc` file so that
the resulting executables have Windows-style resources and
version number information within them.

Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
dscho and others added 30 commits April 8, 2026 02:04
This was pull request git-for-windows#1645 from ZCube/master

Support windows container.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Git for Windows uses MSYS2's Bash to run the test suite, which comes
with benefits but also at a heavy price: on the plus side, MSYS2's
POSIX emulation layer allows us to continue pretending that we are on a
Unix system, e.g. use Unix paths instead of Windows ones, yet this is
bought at a rather noticeable performance penalty.

There *are* some more native ports of Unix shells out there, though,
most notably BusyBox-w32's ash. These native ports do not use any POSIX
emulation layer (or at most a *very* thin one, choosing to avoid
features such as fork() that are expensive to emulate on Windows), and
they use native Windows paths (usually with forward slashes instead of
backslashes, which is perfectly legal in almost all use cases).

And here comes the problem: with a $PWD looking like, say,
C:/git-sdk-64/usr/src/git/t/trash directory.t5813-proto-disable-ssh
Git's test scripts get quite a bit confused, as their assumptions have
been shattered. Not only does this path contain a colon (oh no!), it
also does not start with a slash.

This is a problem e.g. when constructing a URL as t5813 does it:
ssh://remote$PWD. Not only is it impossible to separate the "host" from
the path with a $PWD as above, even prefixing $PWD by a slash won't
work, as /C:/git-sdk-64/... is not a valid path.

As a workaround, detect when $PWD does not start with a slash on
Windows, and simply strip the drive prefix, using an obscure feature of
Windows paths: if an absolute Windows path starts with a slash, it is
implicitly prefixed by the drive prefix of the current directory. As we
are talking about the current directory here, anyway, that strategy
works.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
…ws#4527)

With this patch, Git for Windows works as intended on mounted APFS
volumes (where renaming read-only files would fail).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
On Windows, the current working directory is pretty much guaranteed to
contain a colon. If we feed that path to CVS, it mistakes it for a
separator between host and port, though.

This has not been a problem so far because Git for Windows uses MSYS2's
Bash using a POSIX emulation layer that also pretends that the current
directory is a Unix path (at least as long as we're in a shell script).

However, that is rather limiting, as Git for Windows also explores other
ports of other Unix shells. One of those is BusyBox-w32's ash, which is
a native port (i.e. *not* using any POSIX emulation layer, and certainly
not emulating Unix paths).

So let's just detect if there is a colon in $PWD and punt in that case.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The Git for Windows project has grown quite complex over the years,
certainly much more complex than during the first years where the
`msysgit.git` repository was abusing Git for package management purposes
and the `git/git` fork was called `4msysgit.git`.

Let's describe the status quo in a thorough way.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The TerminateProcess() function does not actually leave the child
processes any chance to perform any cleanup operations. This is bad
insofar as Git itself expects its signal handlers to run.

A symptom is e.g. a left-behind .lock file that would not be left behind
if the same operation was run, say, on Linux.

To remedy this situation, we use an obscure trick: we inject a thread
into the process that needs to be killed and to let that thread run the
ExitProcess() function with the desired exit status. Thanks J Wyman for
describing this trick.

The advantage is that the ExitProcess() function lets the atexit
handlers run. While this is still different from what Git expects (i.e.
running a signal handler), in practice Git sets up signal handlers and
atexit handlers that call the same code to clean up after itself.

In case that the gentle method to terminate the process failed, we still
fall back to calling TerminateProcess(), but in that case we now also
make sure that processes spawned by the spawned process are terminated;
TerminateProcess() does not give the spawned process a chance to do so
itself.

Please note that this change only affects how Git for Windows tries to
terminate processes spawned by Git's own executables. Third-party
software that *calls* Git and wants to terminate it *still* need to make
sure to imitate this gentle method, otherwise this patch will not have
any effect.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The Windows Subsystem for Linux (WSL) version 2 allows to use `chmod` on
NTFS volumes provided that they are mounted with metadata enabled (see
https://devblogs.microsoft.com/commandline/chmod-chown-wsl-improvements/
for details), for example:

	$ chmod 0755 /mnt/d/test/a.sh

In order to facilitate better collaboration between the Windows
version of Git and the WSL version of Git, we can make the Windows
version of Git also support reading and writing NTFS file modes
in a manner compatible with WSL.

Since this slightly slows down operations where lots of files are
created (such as an initial checkout), this feature is only enabled when
`core.WSLCompat` is set to true. Note that you also have to set
`core.fileMode=true` in repositories that have been initialized without
enabling WSL compatibility.

There are several ways to enable metadata loading for NTFS volumes
in WSL, one of which is to modify `/etc/wsl.conf` by adding:

```
[automount]
enabled = true
options = "metadata,umask=027,fmask=117"
```

And reboot WSL.

It can also be enabled temporarily by this incantation:

	$ sudo umount /mnt/c &&
	  sudo mount -t drvfs C: /mnt/c -o metadata,uid=1000,gid=1000,umask=22,fmask=111

It's important to note that this modification is compatible with, but
does not depend on WSL. The helper functions in this commit can operate
independently and functions normally on devices where WSL is not
installed or properly configured.

Signed-off-by: xungeng li <xungeng@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The Git project followed Git for Windows' lead and added their Code of
Conduct, based on the Contributor Covenant v1.4, later updated to v2.0.

We adapt it slightly to Git for Windows.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Previously, we did not install any handler for Ctrl+C, but now we really
want to because the MSYS2 runtime learned the trick to call the
ConsoleCtrlHandler when Ctrl+C was pressed.

With this, hitting Ctrl+C while `git log` is running will only terminate
the Git process, but not the pager. This finally matches the behavior on
Linux and on macOS.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This patch introduces support to set special NTFS attributes that are
interpreted by the Windows Subsystem for Linux as file mode bits, UID
and GID.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Getting started contributing to Git can be difficult on a Windows
machine. CONTRIBUTING.md contains a guide to getting started, including
detailed steps for setting up build tools, running tests, and
submitting patches to upstream.

[includes an example by Pratik Karki how to submit v2, v3, v4, etc.]

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
…ITOR"

In e3f7e01 (Revert "editor: save and reset terminal after calling
EDITOR", 2021-11-22), we reverted the commit wholesale where the
terminal state would be saved and restored before/after calling an
editor.

The reverted commit was intended to fix a problem with Windows Terminal
where simply calling `vi` would cause problems afterwards.

To fix the problem addressed by the revert, but _still_ keep the problem
with Windows Terminal fixed, let's revert the revert, with a twist: we
restrict the save/restore _specifically_ to the case where `vi` (or
`vim`) is called, and do not do the same for any other editor.

This should still catch the majority of the cases, and will bridge the
time until the original patch is re-done in a way that addresses all
concerns.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Handle Ctrl+C in Git Bash nicely

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Includes touch-ups by 마누엘, Philip Oakley and 孙卓识.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
The `--stdin` option was a well-established paradigm in other commands,
therefore we implemented it in `git reset` for use by Visual Studio.

Unfortunately, upstream Git decided that it is time to introduce
`--pathspec-from-file` instead.

To keep backwards-compatibility for some grace period, we therefore
reinstate the `--stdin` option on top of the `--pathspec-from-file`
option, but mark it firmly as deprecated.

Helped-by: Victoria Dye <vdye@github.com>
Helped-by: Matthew John Cheetham <mjcheetham@outlook.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
A fix for calling `vim` in Windows Terminal caused a regression and was
reverted. We partially un-revert this, to get the fix again.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
With improvements by Clive Chan, Adric Norris, Ben Bodenmiller and
Philip Oakley.

Helped-by: Clive Chan <cc@clive.io>
Helped-by: Adric Norris <landstander668@gmail.com>
Helped-by: Ben Bodenmiller <bbodenmiller@hotmail.com>
Helped-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Brendan Forster <brendan@github.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Rather than using private IFTTT Applets that send mails to this
maintainer whenever a new version of a Git for Windows component was
released, let's use the power of GitHub workflows to make this process
publicly visible.

This workflow monitors the Atom/RSS feeds, and opens a ticket whenever a
new version was released.

Note: Bash sometimes releases multiple patched versions within a few
minutes of each other (i.e. 5.1p1 through 5.1p4, 5.0p15 and 5.0p16). The
MSYS2 runtime also has a similar system. We can address those patches as
a group, so we shouldn't get multiple issues about them.

Note further: We're not acting on newlib releases, OpenSSL alphas, Perl
release candidates or non-stable Perl releases. There's no need to open
issues about them.

Co-authored-by: Matthias Aßhauer <mha1993@live.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Reintroduce the 'core.useBuiltinFSMonitor' config setting (originally added
in 0a756b2 (fsmonitor: config settings are repository-specific,
2021-03-05)) after its removal from the upstream version of FSMonitor.

Upstream, the 'core.useBuiltinFSMonitor' setting was rendered obsolete by
"overloading" the 'core.fsmonitor' setting to take a boolean value. However,
several applications (e.g., 'scalar') utilize the original config setting,
so it should be preserved for a deprecation period before complete removal:

* if 'core.fsmonitor' is a boolean, the user is correctly using the new
  config syntax; do not use 'core.useBuiltinFSMonitor'.
* if 'core.fsmonitor' is unspecified, use 'core.useBuiltinFSMonitor'.
* if 'core.fsmonitor' is a path, override and use the builtin FSMonitor if
  'core.useBuiltinFSMonitor' is 'true'; otherwise, use the FSMonitor hook
  indicated by the path.

Additionally, for this deprecation period, advise users to switch to using
'core.fsmonitor' to specify their use of the builtin FSMonitor.

Signed-off-by: Victoria Dye <vdye@github.com>
This topic branch re-adds the deprecated --stdin/-z options to `git
reset`. Those patches were overridden by a different set of options in
the upstream Git project before we could propose `--stdin`.

We offered this in MinGit to applications that wanted a safer way to
pass lots of pathspecs to Git, and these applications will need to be
adjusted.

Instead of `--stdin`, `--pathspec-from-file=-` should be used, and
instead of `-z`, `--pathspec-file-nul`.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Git for Windows accepts pull requests; Core Git does not. Therefore we
need to adjust the template (because it only matches core Git's
project management style, not ours).

Also: direct Git for Windows enhancements to their contributions page,
space out the text for easy reading, and clarify that the mailing list
is plain text, not HTML.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Originally introduced as `core.useBuiltinFSMonitor` in Git for Windows
and developed, improved and stabilized there, the built-in FSMonitor
only made it into upstream Git (after unnecessarily long hemming and
hawing and throwing overly perfectionist style review sticks into the
spokes) as `core.fsmonitor = true`.

In Git for Windows, with this topic branch, we re-introduce the
now-obsolete config setting, with warnings suggesting to existing users
how to switch to the new config setting, with the intention to
ultimately drop the patch at some stage.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This is the recommended way on GitHub to describe policies revolving around
security issues and about supported versions.

Helped-by: Sven Strickroth <email@cs-ware.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
…updates

Start monitoring updates of Git for Windows' component in the open
Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
git-for-windows@1edeb9a
(Win32: warn if the console font doesn't support Unicode,
2014-06-10) introduced both code to detect the current console font on
Windows Vista and newer and a fallback for older systems to detect the
default console font and issue a warning if that font doesn't support
unicode.

Since we haven't supported any Windows older than Vista in almost a
decade, we don't need to keep the workaround.

This more or less fell out of git-for-windows#6108, but didn't quite fit into that PR.

There are also some other version specific hacks and workarounds I
considered dropping, but decided against:

*
git-for-windows@492f709
* I'm unsure if this regression has ever been fixed or just become the
new normal.
* git-for-windows#5042
* So far this hasn't been an issue on Windows 8.1, but officially Go
1.21 and newer only support Windows 10 and newer. So this might become a
problem at any point.
…s#6108)

While the currently used way to detect the number of CPU cores ond
Windows is nice and straight-forward, GetSystemInfo() only [gives us
access to the number of processors within the current
group.](https://learn.microsoft.com/en-us/windows/win32/api/sysinfoapi/ns-sysinfoapi-system_info#members)

While that is usually fine for systems with a single physical CPU,
separate physical sockets are typically separate groups.

Switch to using GetLogicalProcessorInformationEx() to handle
multi-socket
systems better.

I've tested this on a physical single-socket x86-64 and a physical
dual-socket x86-64 system, and on a virtual single-socket ARM64 system.
Physical [multi-socket ARM64 systems seem to
exist](https://cloudbase.it/ampere-altra-industry-leading-arm64-server/),
but I don't have access to such hardware and the hypervisor I use
apparently can't emulate that either.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.