Jeff King wrote:
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -377,10 +377,40 @@ static void remove_junk(void)
> static const char *junk_work_tree;
> static const char *junk_git_dir;
> static pid_t junk_pid;
> +enum {
> + JUNK_LEAVE_NONE,
> + JUNK_LEAVE_REPO,
> + JUNK_LEAVE_ALL
> +} junk_mode = JUNK_LEAVE_NONE;
Neat.
> +
> +static const char junk_leave_repo_msg[] =
> +N_("The remote repository was cloned successfully, but there was\n"
> + "an error checking out the HEAD branch. The repository has been left in\n"
> + "place but the working tree may be in an inconsistent state. You can\n"
> + "can inspect the contents with:\n"
> + "\n"
> + " git status\n"
> + "\n"
> + "and retry the checkout with\n"
> + "\n"
> + " git checkout -f HEAD\n"
> + "\n");
Can this be made more precise? I don't know what it means for the
working tree to be in an inconsistent state: do you mean that some files
might be partially checked out or not have been checked out at all yet?
error: Clone succeeded, but checkout failed.
hint: You can inspect what was checked out with "git status".
hint: To retry the checkout, run "git checkout -f HEAD".
Aside from that, this looks very nice.
Thanks,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
