From: Brandon Williams <bmwill@google.com>
To: Stefan Beller <sbeller@google.com>
Cc: jrnieder@gmail.com, git@vger.kernel.org
Subject: Re: [RFC PATCH 4/5] submodule--helper: reattach-HEAD
Date: Mon, 1 May 2017 11:36:56 -0700 [thread overview]
Message-ID: <20170501183656.GH39135@google.com> (raw)
In-Reply-To: <20170501180058.8063-5-sbeller@google.com>
On 05/01, Stefan Beller wrote:
> Add a new command, that reattaches a detached HEAD to its configured
> branch in a submodule.
>
> In a later patch we will teach git-submodule as well as other submodule
> worktree manipulators (git reset/checkout --recurse-submodules) to not
> end up in a detached HEAD state in the submodules.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
>
> +int reattach_HEAD(const char *submodule_path, int flags)
> +{
> + const char *branch;
> + struct object_id sub_head_object;
> + struct object_id sub_branch_object;
> +
> + const struct submodule *sub = submodule_from_path(null_sha1, submodule_path);
> +
> + if (!sub) {
> + if (!(flags & REATTACH_HEAD_DIE_ON_ERROR))
> + return -1;
> + die(_("no submodule mapping found in .gitmodules for path '%s'"),
> + submodule_path);
It may be a bit clearer to do the following:
if (flags & REATTACH_HEAD_DIE_ON_ERROR)
die(...);
return -1;
It just feels weird to me to have the inverted logic, that's my opinion
though.
> + }
> +
> + if (!sub->branch) {
> + if (!(flags & REATTACH_HEAD_DIE_ON_ERROR))
> + return -1;
> + die(_("no branch configured to follow for submodule '%s'"),
> + sub->path);
> + }
> +
> + /* lookup branch value in .gitmodules */
> + if (strcmp(".", sub->branch)) {
> + branch = sub->branch;
> + } else {
> + /* special care for '.': Is the superproject on a branch? */
> + struct object_id oid;
> + branch = resolve_refdup("HEAD", 0, oid.hash, NULL);
> + if (!branch) {
> + if (!(flags & REATTACH_HEAD_DIE_ON_ERROR))
> + return -1;
> + die(_("Not on any branch, but submodule configured to follow superprojects branch"));
> + }
> + }
> +
> + if (!strcmp("HEAD", branch))
> + return 0;
So this is the case where the superproject is in a detached-HEAD state?
In that case then we don't need to continue because if the superproject
isn't on a branch, then there isn't a reason the submodule should be on
a branch.
> +
> + resolve_gitlink_ref(sub->path, "HEAD", sub_head_object.hash);
> + resolve_gitlink_ref(sub->path, branch, sub_branch_object.hash);
> +
> + if (!oidcmp(&sub_head_object, &sub_branch_object)) {
> + struct child_process cp = CHILD_PROCESS_INIT;
> + struct strbuf reason = STRBUF_INIT;
> +
> + cp.dir = sub->path;
> + prepare_submodule_repo_env(&cp.env_array);
> +
> + strbuf_addf(&reason, "reattach HEAD to %s", branch);
> + argv_array_pushl(&cp.args, "git", "symbolic-ref",
> + "-m", reason.buf, "HEAD", branch, NULL);
> + if (run_command(&cp)) {
> + if (!(flags & REATTACH_HEAD_DIE_ON_ERROR))
> + return -1;
> + die(_("could not run symbolic-ref in submodule '%s'"),
> + sub->path);
> + }
> + strbuf_release(&reason);
> + return 0;
> + } else {
> + fprintf(stderr, "not reattaching HEAD, object ids differ:\n"
> + "HEAD is %s\n branch is %s",
> + oid_to_hex(&sub_head_object),
> + oid_to_hex(&sub_branch_object));
> + return 1;
> + }
> +}
> +
> static int find_first_merges(struct object_array *result, const char *path,
> struct commit *a, struct commit *b)
> {
> diff --git a/submodule.h b/submodule.h
> index 1277480add..f7bb565a6d 100644
> --- a/submodule.h
> +++ b/submodule.h
> @@ -119,6 +119,16 @@ extern int submodule_move_head(const char *path,
> */
> extern void prepare_submodule_repo_env(struct argv_array *out);
>
> +/*
> + * Attach the submodules HEAD to its configured branch if the underlying
> + * object id are the same. Returns
> + * - 0 when the branch could be reattached.
> + * - +1 when the branch could not be reattached due to object name mismatch
> + * - <0 when an error occurred (e.g. missing .gitmodules file)
> + */
> +#define REATTACH_HEAD_DIE_ON_ERROR (1<<0)
> +extern int reattach_HEAD(const char *submodule_path, int flags);
> +
> #define ABSORB_GITDIR_RECURSE_SUBMODULES (1<<0)
> extern void absorb_git_dir_into_superproject(const char *prefix,
> const char *path,
> --
> 2.13.0.rc1.1.gbc33f0f778
>
--
Brandon Williams
next prev parent reply other threads:[~2017-05-01 18:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 18:00 [PATCH 0/5] Some submodule bugfixes and "reattaching detached HEADs" Stefan Beller
2017-05-01 18:00 ` [PATCH 1/5] submodule_move_head: fix leak of struct child_process Stefan Beller
2017-05-01 18:06 ` Brandon Williams
2017-05-02 3:07 ` Junio C Hamano
2017-05-02 4:20 ` Stefan Beller
2017-05-01 18:00 ` [PATCH 2/5] submodule_move_head: prepare env for child correctly Stefan Beller
2017-05-02 2:04 ` Junio C Hamano
2017-05-02 4:18 ` Stefan Beller
2017-05-01 18:00 ` [PATCH 3/5] submodule: avoid auto-discovery in new working tree manipulator code Stefan Beller
2017-05-01 18:00 ` [RFC PATCH 4/5] submodule--helper: reattach-HEAD Stefan Beller
2017-05-01 18:36 ` Brandon Williams [this message]
2017-05-01 19:00 ` Stefan Beller
2017-05-01 18:00 ` [RFC PATCH 5/5] submodule_move_head: reattach submodule HEAD to branch if possible Stefan Beller
2017-05-01 18:24 ` [PATCH 0/5] Some submodule bugfixes and "reattaching detached HEADs" Brandon Williams
2017-05-02 1:35 ` Junio C Hamano
2017-05-02 4:04 ` Stefan Beller
2017-05-31 22:09 ` Stefan Beller
2017-05-02 19:32 ` [PATCHv2 0/3] Some submodule bugfixes Stefan Beller
2017-05-02 19:32 ` [PATCHv2 1/3] submodule_move_head: reuse child_process structure for futher commands Stefan Beller
2017-05-02 19:32 ` [PATCHv2 2/3] submodule: avoid auto-discovery in new working tree manipulator code Stefan Beller
2017-05-02 19:32 ` [PATCHv2 3/3] submodule: properly recurse for read-tree and checkout Stefan Beller
2017-05-02 19:42 ` [PATCHv2 0/3] Some submodule bugfixes Brandon Williams
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=20170501183656.GH39135@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.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).