From: Junio C Hamano <gitster@pobox.com>
To: Marco Costalba <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH TAKE 2] Avoid a useless prefix lookup in strbuf_expand()
Date: Sat, 09 Feb 2008 18:36:08 -0800 [thread overview]
Message-ID: <7vr6fl5yhz.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1202568019-20200-1-git-send-email-mcostalba@gmail.com> (Marco Costalba's message of "Sat, 9 Feb 2008 15:40:19 +0100")
Marco Costalba <mcostalba@gmail.com> writes:
> Currently the --prett=format prefix is looked up in a
s/prett/&y/;
> New patch with Junio suggestions included.
Hmph, this is a blast from the past.
I do recall pointing out that a rather common "format:%an <%ae>"
ends up parsing the same line twice, and mentioned we may want
to memoise the first call's result in the format_commit_context
structure, but what else did I suggest???
Anyway, I'll take a look later. Thanks.
next prev parent reply other threads:[~2008-02-10 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 14:40 [PATCH TAKE 2] Avoid a useless prefix lookup in strbuf_expand() Marco Costalba
2008-02-10 2:36 ` Junio C Hamano [this message]
2008-02-10 6:59 ` Marco Costalba
2008-02-10 10:52 ` Junio C Hamano
2008-02-10 2:52 ` Johannes Schindelin
2008-02-10 7:00 ` Marco Costalba
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=7vr6fl5yhz.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@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 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).