From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
ps@pks.im, Eric Sunshine <sunshine@sunshineco.com>,
Stefan Beller <sbeller@google.com>,
Lars Schneider <larsxschneider@gmail.com>,
Michael Blume <blume.mike@gmail.com>
Subject: [PATCH v6 05/15] submodule: die on config error when linking modules
Date: Mon, 22 Feb 2016 12:23:26 +0100 [thread overview]
Message-ID: <1456140216-24169-6-git-send-email-ps@pks.im> (raw)
In-Reply-To: <1456140216-24169-1-git-send-email-ps@pks.im>
When trying to connect a submodule with its corresponding
repository in '.git/modules' we try to set the core.worktree
setting in the submodule, which may fail due to an error
encountered in `git_config_set_in_file`.
The function is used in the git-mv command when trying to move a
submodule to another location. We already die when renaming a
file fails but do not pay attention to the case where updating
the connection between submodule and its repository fails. As
this leaves the repository in an inconsistent state, as well,
abort the program by dying early and presenting the failure to
the user.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
---
submodule.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/submodule.c b/submodule.c
index b83939c..589a82c 100644
--- a/submodule.c
+++ b/submodule.c
@@ -1087,11 +1087,9 @@ void connect_work_tree_and_git_dir(const char *work_tree, const char *git_dir)
/* Update core.worktree setting */
strbuf_reset(&file_name);
strbuf_addf(&file_name, "%s/config", git_dir);
- if (git_config_set_in_file(file_name.buf, "core.worktree",
- relative_path(real_work_tree, git_dir,
- &rel_path)))
- die(_("Could not set core.worktree in %s"),
- file_name.buf);
+ git_config_set_in_file_or_die(file_name.buf, "core.worktree",
+ relative_path(real_work_tree, git_dir,
+ &rel_path));
strbuf_release(&file_name);
strbuf_release(&rel_path);
--
2.7.1
next prev parent reply other threads:[~2016-02-22 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 11:23 [PATCH v6 00/15] config: make git_config_set die on failure Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 01/15] config: introduce set_or_die wrappers Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 02/15] branch: report errors in tracking branch setup Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 03/15] branch: die on config error when unsetting upstream Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 04/15] branch: die on config error when editing branch description Patrick Steinhardt
2016-02-22 11:23 ` Patrick Steinhardt [this message]
2016-02-22 11:23 ` [PATCH v6 06/15] submodule--helper: die on config error when cloning module Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 07/15] remote: die on config error when setting URL Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 08/15] remote: die on config error when setting/adding branches Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 09/15] remote: die on config error when manipulating remotes Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 10/15] clone: die on config error in cmd_clone Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 11/15] init-db: die on config errors when initializing empty repo Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 12/15] sequencer: die on config error when saving replay opts Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 13/15] compat: die when unable to set core.precomposeunicode Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 14/15] config: rename git_config_set to git_config_set_gently Patrick Steinhardt
2016-02-22 11:23 ` [PATCH v6 15/15] config: rename git_config_set_or_die to git_config_set Patrick Steinhardt
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=1456140216-24169-6-git-send-email-ps@pks.im \
--to=ps@pks.im \
--cc=blume.mike@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--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).