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, #02; Mon, 11)
Date: Tue, 12 Sep 2017 13:30:44 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1709121326410.4132@virtualbox> (raw)
In-Reply-To: <xmqqpoay3tgz.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Mon, 11 Sep 2017, Junio C Hamano wrote:
> * js/rebase-i-final (2017-07-27) 10 commits
> - rebase -i: rearrange fixup/squash lines using the rebase--helper
> - t3415: test fixup with wrapped oneline
> - rebase -i: skip unnecessary picks using the rebase--helper
> - rebase -i: check for missing commits in the rebase--helper
> - t3404: relax rebase.missingCommitsCheck tests
> - rebase -i: also expand/collapse the SHA-1s via the rebase--helper
> - rebase -i: do not invent onelines when expanding/collapsing SHA-1s
> - rebase -i: remove useless indentation
> - rebase -i: generate the script via rebase--helper
> - t3415: verify that an empty instructionFormat is handled as before
>
> The final batch to "git rebase -i" updates to move more code from
> the shell script to C.
>
> Expecting a reroll.
No you don't: xmqqfudqkcux.fsf@gitster.mtv.corp.google.com
> [...]
>
> --------------------------------------------------
> [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]
>
> [...]
This section would be more appropriate for the three "Dropped" patch
series than the "Cooking" section.
Ciao,
Dscho
prev parent reply other threads:[~2017-09-12 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 1:38 What's cooking in git.git (Sep 2017, #02; Mon, 11) Junio C Hamano
2017-09-11 19:26 ` Kevin Willford
2017-09-11 19:53 ` Thomas Gummerer
2017-09-12 2:16 ` Junio C Hamano
2017-09-12 11:30 ` Johannes Schindelin [this message]
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=alpine.DEB.2.21.1.1709121326410.4132@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox