git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Kevin Bracey <kevin@bracey.fi>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] checkout: abbreviate hash in suggest_reattach
Date: Mon, 8 Apr 2013 17:03:03 -0400	[thread overview]
Message-ID: <20130408210303.GA9649@sigill.intra.peff.net> (raw)
In-Reply-To: <1365436422-25554-1-git-send-email-kevin@bracey.fi>

On Mon, Apr 08, 2013 at 06:53:42PM +0300, Kevin Bracey wrote:

> After printing the list of left-behind commits (with abbreviated
> hashes), use an abbreviated hash in the suggested 'git branch' command;
> there's no point in outputting a full 40-character hex string in some
> friendly advice.
> 
> Signed-off-by: Kevin Bracey <kevin@bracey.fi>

I think this makes sense. We generally use the full sha1 when the output
is meant to live for a long time, but that is not the case here.

I suspect I would have been annoyed by it, too, if I did not have
advice.detachedHEAD turned off. :)

> diff --git a/builtin/checkout.c b/builtin/checkout.c
> index a9c1b5a..e168bfb 100644
> --- a/builtin/checkout.c
> +++ b/builtin/checkout.c
> @@ -700,7 +700,7 @@ static void suggest_reattach(struct commit *commit, struct rev_info *revs)
>  			"If you want to keep them by creating a new branch, "
>  			"this may be a good time\nto do so with:\n\n"
>  			" git branch new_branch_name %s\n\n"),
> -			sha1_to_hex(commit->object.sha1));
> +			find_unique_abbrev(commit->object.sha1, DEFAULT_ABBREV));
>  }

Code looks obviously correct to me.

Acked-by: Jeff King <peff@peff.net>

-Peff

      reply	other threads:[~2013-04-08 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 15:53 [PATCH] checkout: abbreviate hash in suggest_reattach Kevin Bracey
2013-04-08 21:03 ` Jeff King [this message]

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=20130408210303.GA9649@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kevin@bracey.fi \
    /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).