From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] hex.c: reduce memory footprint of sha1_to_hex static buffers
Date: Fri, 13 Feb 2015 13:58:42 -0800 [thread overview]
Message-ID: <CA+55aFyTcU0zjo9rTxetnRj72YS+Mo52sx85-Rk0woXEbQVfsw@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kaEun-mEQPg7cmPV7RJR8A+BxSsSpeAQgcsuJn8L4TGEg@mail.gmail.com>
On Fri, Feb 13, 2015 at 1:56 PM, Stefan Beller <sbeller@google.com> wrote:
>
> As I could not find any documentation on the
> magical 50 in the early days, I cc'd Linus
> in case there is something I did not think of yet.
Nothing magical, it's just "rounded up from 40 + NUL character".
Linus
next prev parent reply other threads:[~2015-02-13 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 21:18 [PATCH] hex.c: reduce memory footprint of sha1_to_hex static buffers Stefan Beller
2015-02-13 21:41 ` Junio C Hamano
2015-02-13 21:56 ` Stefan Beller
2015-02-13 21:58 ` Linus Torvalds [this message]
2015-02-13 23:45 ` 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=CA+55aFyTcU0zjo9rTxetnRj72YS+Mo52sx85-Rk0woXEbQVfsw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).