[PATCH] sh-setup: Explicitly set IFS to its default, instead of unsetting it.

From: Marc Branchaud Some sh implementations interpret "unset IFS" to mean IFS=''. This was seen in FreeBSD 7.2's sh. We need to make sure IFS has its default value: . Signed-off-by: Marc Branchaud --- git-sh-setup.sh | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a

[PATCH 2/6] Teach remote.c about the remote.default configuration setting.

From: Marc Branchaud The code now has a default_remote_name and an effective_remote_name: - default_remote_name is set by remote.default in the config, or is "origin" if remote.default doesn't exist ("origin" was the fallback value before this change). - effective_remote_name is the nam

[PATCH 1/6] Rename remote.c's default_remote_name static variables.

From: Marc Branchaud This prepares the code to handle a true remote.default configuration value. Rename two variables: default_remote_name --> effective_remote_name explicit_default_remote_name --> explicit_effective_remote_name effective_remote_name is the remote name that is curr

[PATCH 6/6] Teach get_default_remote to respect remote.default.

From: Marc Branchaud Use "git remote default" instead of replicating its logic. The unit test checks a relative-path submodule because the submodule code is (almost) the only thing that uses get_default_remote. Signed-off-by: Marc Branchaud --- git-parse-remote.sh| 5 + t/t7400-s

[PATCH 5/6] Test that plain "git fetch" uses remote.default when on a detached HEAD.

From: Marc Branchaud Signed-off-by: Marc Branchaud --- t/t5510-fetch.sh | 17 + 1 file changed, 17 insertions(+) diff --git a/t/t5510-fetch.sh b/t/t5510-fetch.sh index d7a19a1..8ecd996 100755 --- a/t/t5510-fetch.sh +++ b/t/t5510-fetch.sh @@ -69,6 +69,23 @@ test_expect_success "

[PATCH v2 0/6] Default remote

Incorporated feedback on the first version of this series[1], and also added documentation updates. Note that the documentation changes include 4 minor grammatical fixes (verb tenses, added a "the" in a couple fo places). I also added Phil's "git push" scenario to patch #2's message, rather tha

[PATCH 4/6] Teach clone to set remote.default.

From: Marc Branchaud This makes git-clone consistent with the remote.default support implemented in git-remote. Specifically, since "git remote add" sets remote.default if it's adding the first remote to the repository, when clone itself adds the first remote it should do the same. This also ma

[PATCH 3/6] Teach "git remote" about remote.default.

From: Marc Branchaud The "rename" and "rm" commands now handle the case where the remote being changed is the default remote. If the "add" command is used to add the repo's first remote, that remote becomes the default remote. Also introduce a "default" sub-command to get or set the default rem