From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
Date: Fri, 15 Sep 2017 21:23:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1709152122360.219280@virtualbox> (raw)
In-Reply-To: <xmqq8thgy03t.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Fri, 15 Sep 2017, Junio C Hamano wrote:
> --------------------------------------------------
> [Cooking]
>
> [...]
>
> * mk/diff-delta-uint-may-be-shorter-than-ulong (2017-08-10) 1 commit
> . diff-delta: fix encoding size that would not fit in "unsigned int"
>
> The machinery to create xdelta used in pack files received the
> sizes of the data in size_t, but lost the higher bits of them by
> storing them in "unsigned int" during the computation, which is
> fixed.
>
> Dropped, as it was rerolled for review as part of a larger series.
> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause>
>
> [...]
>
> * mk/use-size-t-in-zlib (2017-08-10) 1 commit
> . zlib.c: use size_t for size
>
> The wrapper to call into zlib followed our long tradition to use
> "unsigned long" for sizes of regions in memory, which have been
> updated to use "size_t".
>
> Dropped, as it was rerolled for review as part of a larger series.
> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause>
>
>
> * mk/diff-delta-avoid-large-offset (2017-08-11) 1 commit
> . diff-delta: do not allow delta offset truncation
>
> The delta format used in the packfile cannot reference data at
> offset larger than what can be expressed in 4-byte, but the
> generator for the data failed to make sure the offset does not
> overflow. This has been corrected.
>
> Dropped, as it was rerolled for review as part of a larger series.
> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause>
>
>
> --------------------------------------------------
> [Discarded]
>
> [...]
These three topics are still in the wrong category. Please fix.
Ciao,
Dscho
next prev parent reply other threads:[~2017-09-15 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:58 What's cooking in git.git (Sep 2017, #03; Fri, 15) Junio C Hamano
2017-09-15 7:50 ` Lars Schneider
2017-09-19 1:18 ` Junio C Hamano
2017-09-15 19:14 ` Johannes Schindelin
2017-09-15 20:33 ` Junio C Hamano
2017-09-15 19:23 ` Johannes Schindelin [this message]
2017-09-15 20:49 ` Junio C Hamano
2017-09-29 11:39 ` Johannes Schindelin
2017-09-21 21:14 ` Sahil Dua
2017-09-22 0:59 ` Junio C Hamano
2017-09-22 3:39 ` Junio C Hamano
2017-09-24 16:16 ` Sahil Dua
2017-09-25 0:40 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1.1709152122360.219280@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).