From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff_unique_abbrev(): document its assumtion and limitation
Date: Fri, 30 Sep 2016 14:09:57 -0400 [thread overview]
Message-ID: <20160930180957.xj4jqoslbtevhqpb@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqvaxd9ssy.fsf@gitster.mtv.corp.google.com>
On Fri, Sep 30, 2016 at 10:54:53AM -0700, Junio C Hamano wrote:
> This function is used to add "..." to displayed object names in
> "diff --raw --abbrev[=<n>]" output. It bases its behaviour on an
> untold assumption that the abbreviation length requested by the
> caller is "reasonble", i.e. most of the objects will abbreviate
> within the requested length and the resulting length would never
> exceed it by more than a few hexdigits (otherwise the resulting
> columns would not align). Explain that in a comment.
Heh, I have actually have a similar patch that renames it to
diff_aligned_abbrev(). Because I wanted to add another function:
static const char *diff_abbrev_oid(const struct object_id *oid,
int abbrev)
{
if (startup_info->have-repository)
return find_unique_abbrev(oid->hash, abbrev);
else {
char *hex = oid_to_hex(oid);
if (abbrev < 0) || abbrev > GIT_SHA1_HEXSZ)
die("BUG: oid abbreviation out of range: %d", abbrev);
hex[abbrev] = '\0';
return hex;
}
}
and I didn't want people to confuse the two. Now that function _would_
want to be updated as a result of the other conversation (it would need
to do something sensible with "-1", like turning it into "7", or
whatever else is deemed reasonable outside of a repository).
Anyway. I just wonder if you want to give it a better name while you are
at it.
-Peff
next prev parent reply other threads:[~2016-09-30 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 17:54 [PATCH] diff_unique_abbrev(): document its assumtion and limitation Junio C Hamano
2016-09-30 18:09 ` Jeff King [this message]
2016-09-30 19:19 ` Junio C Hamano
2016-10-01 9:15 ` Jeff King
2016-10-03 17:08 ` Junio C Hamano
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=20160930180957.xj4jqoslbtevhqpb@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).