From: Junio C Hamano <gitster@pobox.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: "git\@vger.kernel.org list" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2015, #01; Thu, 2)
Date: Fri, 03 Apr 2015 14:28:43 -0700 [thread overview]
Message-ID: <xmqqpp7kgaus.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <155011F7-1806-4226-B085-F1F4206062C6@gmail.com> (Kyle J. McKay's message of "Thu, 2 Apr 2015 17:55:55 -0700")
"Kyle J. McKay" <mackyle@gmail.com> writes:
> On Apr 2, 2015, at 15:09, Junio C Hamano wrote:
>
>> * jc/show-branch (2014-03-24) 5 commits
>> - show-branch: use commit slab to represent bitflags of arbitrary
>> width
>> - show-branch.c: remove "all_mask"
>> - show-branch.c: abstract out "flags" operation
>> - show-branch.c: lift all_mask/all_revs to a global static
>> - show-branch.c: update comment style
>>
>> Waiting for the final step to lift the hard-limit before sending it
>> out.
>
>
> May I ask, now that this topic is over 1-year old, please, what is the
> final step?
It would be to "lift the hard-limit"; all the existing changes are
to allow the limit to be lifted by moving from "bits in a word-sized
field" to "commit-slab that can hold arbitrary number of bits".
>
> Perhaps someone might submit a patch... ;)
>
> -Kyle
prev parent reply other threads:[~2015-04-03 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 22:09 What's cooking in git.git (Apr 2015, #01; Thu, 2) Junio C Hamano
2015-04-03 0:55 ` Kyle J. McKay
2015-04-03 21:28 ` Junio C Hamano [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=xmqqpp7kgaus.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.