From: Junio C Hamano <gitster@pobox.com>
To: Marco Costalba <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RESEND] Avoid a useless prefix lookup in strbuf_expand()
Date: Mon, 04 Feb 2008 23:00:43 -0800 [thread overview]
Message-ID: <7vtzknga5g.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1201950593-6119-1-git-send-email-mcostalba@gmail.com> (Marco Costalba's message of "Sat, 2 Feb 2008 12:09:53 +0100")
Marco Costalba <mcostalba@gmail.com> writes:
> Currently the --prett=format prefix is looked up in a
> ...
> diff --git a/pretty.c b/pretty.c
> index b987ff2..64ead65 100644
> --- a/pretty.c
> +++ b/pretty.c
> @@ -282,16 +282,18 @@ static char *logmsg_reencode(const struct commit *commit,
> return out;
> }
>
> -static void format_person_part(struct strbuf *sb, char part,
> +/* returns placeholder length or 0 if placeholder is not known */
> +static size_t format_person_part(struct strbuf *sb, char part,
> const char *msg, int len)
> {
> - int start, end, tz = 0;
> - unsigned long date;
> + int start, end, tz = 0, end_of_data;
> + unsigned long date = 0;
> char *ep;
>
> - /* parse name */
> + /* advance 'end' to point to email start delimiter */
> for (end = 0; end < len && msg[end] != '<'; end++)
> ; /* do nothing */
> +
Another thing I noticed is that --pretty='format:%an %ae %at'
would end up running this function three times. Perhaps it is
worth memoizing the result in format_commit_context while you
are at it?
next prev parent reply other threads:[~2008-02-05 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 11:09 [PATCH RESEND] Avoid a useless prefix lookup in strbuf_expand() Marco Costalba
2008-02-03 21:53 ` Junio C Hamano
2008-02-03 22:22 ` Marco Costalba
2008-02-05 7:00 ` Junio C Hamano [this message]
2008-02-05 13:17 ` 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=7vtzknga5g.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).