From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] auto-sizing default abbreviation length
Date: Fri, 30 Sep 2016 17:19:34 -0700 [thread overview]
Message-ID: <20161001001937.10884-1-gitster@pobox.com> (raw)
So here is what I queued in 'pu' tonight after back and forth with
Linus and Peff. The third step from Linus needs to be signed off
and also a meaningful log message for it needs to be written, and
also may need to be updated to include what Linus did in [*1*], but
otherwise I think these are in good enough shape for people to start
playing with them.
They apply on top of Peff's jk/ambiguous-short-object-names topic
that ends at 5b33cb1fd7 ("get_short_sha1: make default
disambiguation configurable", 2016-09-27).
*1*
http://public-inbox.org/git/<CA+55aFxyF=xX84AXr8MG14MRHwdrQw00PBM20UfqBdidaeqdMg@mail.gmail.com>
Junio C Hamano (2):
abbrev: add FALLBACK_DEFAULT_ABBREV to prepare for auto sizing
abbrev: prepare for new world order
Linus Torvalds (1):
abbrev: auto size the default abbreviation
builtin/fetch.c | 3 +++
builtin/rev-parse.c | 5 +++--
cache.h | 4 ++++
diff.c | 25 +++++++++++++++++++++++--
environment.c | 2 +-
sha1_name.c | 28 +++++++++++++++++++++++++++-
transport.h | 3 +--
7 files changed, 62 insertions(+), 8 deletions(-)
--
2.10.0-622-g05f606bbb0
next reply other threads:[~2016-10-01 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 0:19 Junio C Hamano [this message]
2016-10-01 0:19 ` [PATCH 1/3] abbrev: add FALLBACK_DEFAULT_ABBREV to prepare for auto sizing Junio C Hamano
2016-10-01 0:19 ` [PATCH 2/3] abbrev: prepare for new world order Junio C Hamano
2016-10-01 0:19 ` [PATCH 3/3] abbrev: auto size the default abbreviation Junio C Hamano
2016-10-03 22:27 ` Jeff King
2016-10-03 22:34 ` Linus Torvalds
2016-10-03 22:40 ` Jeff King
2016-10-03 22:52 ` Junio C Hamano
2016-10-03 23:47 ` Jeff King
2016-10-04 1:37 ` Junio C Hamano
2016-10-04 12:18 ` Jeff King
2016-11-02 1:33 ` Junio C Hamano
2016-11-02 2:12 ` Jeff King
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=20161001001937.10884-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).