Matthieu Moy <Matthieu.Moy@xxxxxxx> writes:
> In both cases, give a hint on what to do next. We mention explicitely
> "detached HEAD" since this is the keyword to look for in documentations.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@xxxxxxx>
> ---
> builtin/push.c | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/push.c b/builtin/push.c
> index 210eb36..48fb050 100644
> --- a/builtin/push.c
> +++ b/builtin/push.c
> @@ -69,7 +69,8 @@ static void setup_push_upstream(struct remote *remote)
> struct strbuf refspec = STRBUF_INIT;
> struct branch *branch = branch_get(NULL);
> if (!branch)
> - die("You are not currently on a branch.");
> + die("You are not currently on a branch (detached HEAD).\n"
> + "Please, checkout the branch you want to push first or specify it on the command line.");
I agree that it is a good thing to suggest specifying what to push on the
command line, but I don't think this "checkout first" is particularly a
good advice, as it requires two-step operation that is quite a roundabout
way of doing what the user wanted to do: a very specific checkout followed
by re-running of a nonspecific push.
> @@ -152,7 +153,14 @@ static int do_push(const char *repo, int flags)
> if (!remote) {
> if (repo)
> die("bad repository '%s'", repo);
> - die("No destination configured to push to.");
> + die("No destination configured to push to.\n"
> + "Either specify the URL from the command line or configure a remote repository using\n"
> + "\n"
> + " git remote add <name> <url>\n"
> + "\n"
> + "and then push using the remote name like\n"
> + "\n"
> + " git push <name>\n");
> }
This one would be helpful.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html