From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (May 2013, #05; Mon, 20)
Date: Thu, 23 May 2013 12:07:12 +0200 [thread overview]
Message-ID: <519DEA50.4030407@drmicha.warpmail.net> (raw)
In-Reply-To: <7vy5b7j7kc.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 22.05.2013 18:36:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>
>>> * mg/more-textconv (2013-05-10) 7 commits
>>> - grep: honor --textconv for the case rev:path
>>> - grep: allow to use textconv filters
>>> - t7008: demonstrate behavior of grep with textconv
>>> - cat-file: do not die on --textconv without textconv filters
>>> - show: honor --textconv for blobs
>>> - diff_opt: track whether flags have been set explicitly
>>> - t4030: demonstrate behavior of show with textconv
>>>
>>> I think this is ready for 'next'; not that it matters during the
>>> prerelease feature freeze.
>>
>> Oh, I'm sorry, I thought we were still in discussions about the default
>> mechanism (config or attributes) and the implementation (tacking context
>> onto each object)? Therefore, I didn't hurry to polish and follow up
>> over my vacation. I'm not sure I had smoothed out all minor things
>> (honor/obey and such) when the object struct size issue came up. I'll
>> check today or tomorrow. (Freeze, yes, but we don't want too many next
>> rewrites, and one is coming soon...)
>
> I thought this was fine as-is, but we can kick it back to 'pu' and
> replace it with a reroll after 1.8.3 if that is necessary.
Didn't you have concerns about storing the context in the object struct?
I can't quite judge how much of an issue this can be for fsck and such.
I don't want to increase the memory footprint unnecessarily, of course.
Other than that, the mechanism was still up for discussion (separate
"show" attribute or a config) given that the default behavior for
showing blobs is not to change.
Michael
next prev parent reply other threads:[~2013-05-23 10:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 0:15 What's cooking in git.git (May 2013, #05; Mon, 20) Junio C Hamano
2013-05-21 0:22 ` Felipe Contreras
2013-05-21 1:16 ` Johan Herland
2013-05-21 15:35 ` Junio C Hamano
2013-05-22 7:49 ` Johan Herland
2013-07-01 21:56 ` Junio C Hamano
2013-07-02 13:02 ` Johan Herland
2013-05-21 7:19 ` Thomas Rast
2013-05-21 15:36 ` Junio C Hamano
2013-05-29 5:19 ` Jeff King
2013-05-21 11:47 ` activate color.ui by default (Re: What's cooking in git.git (May 2013, #05; Mon, 20)) Matthieu Moy
2013-05-21 15:52 ` Junio C Hamano
2013-05-22 7:30 ` What's cooking in git.git (May 2013, #05; Mon, 20) Michael J Gruber
2013-05-22 7:36 ` Michael J Gruber
2013-05-22 16:36 ` Junio C Hamano
2013-05-23 10:07 ` Michael J Gruber [this message]
2013-05-23 14:40 ` Junio C Hamano
2013-05-23 15:31 ` Michael J Gruber
2013-05-23 17:37 ` 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=519DEA50.4030407@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.