From: Thomas Rast <trast@student•ethz.ch>
To: Jeff King <peff@peff•net>
Cc: Junio C Hamano <gitster@pobox•com>, <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Mar 2013, #07; Tue, 26)
Date: Wed, 27 Mar 2013 21:50:34 +0100 [thread overview]
Message-ID: <878v58worp.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <20130327203535.GA5220@sigill.intra.peff.net> (Jeff King's message of "Wed, 27 Mar 2013 16:35:35 -0400")
Jeff King <peff@peff•net> writes:
> On Tue, Mar 26, 2013 at 03:40:00PM -0700, Junio C Hamano wrote:
>
>> [Cooking]
>> [...]
>> * jk/index-pack-correct-depth-fix (2013-03-20) 1 commit
>> - index-pack: always zero-initialize object_entry list
>>
>> "index-pack --fix-thin" used uninitialize value to compute delta
>> depths of objects it appends to the resulting pack.
>
> Any reason this is still in pu? I'd have expected it to be fairly
> uncontroversial and slated for maint.
Me too, along with the other two we found in the same topic:
> * nd/index-pack-threaded-fixes (2013-03-19) 2 commits
> - index-pack: guard nr_resolved_deltas reads by lock
> - index-pack: protect deepest_delta in multithread code
>
> "index-pack --verify-stat" used a few counters outside protection
> of mutex, possibly showing incorrect numbers.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-03-27 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 22:40 What's cooking in git.git (Mar 2013, #07; Tue, 26) Junio C Hamano
2013-03-27 20:35 ` Jeff King
2013-03-27 20:50 ` Junio C Hamano
2013-03-27 20:52 ` Jeff King
2013-03-27 20:50 ` Thomas Rast [this message]
2013-03-27 21:47 ` Junio C Hamano
2013-03-27 22:07 ` John Keeping
2013-03-27 22:15 ` Junio C Hamano
2013-03-27 22:52 ` John Keeping
2013-03-28 21:40 ` Junio C Hamano
2013-03-27 22:25 ` jn/add-2.0-u-A-sans-pathspec (Re: What's cooking in git.git (Mar 2013, #07; Tue, 26)) Jonathan Nieder
2013-03-28 8:00 ` What's cooking in git.git (Mar 2013, #07; Tue, 26) Thomas Rast
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=878v58worp.fsf@linux-k42r.v.cablecom.net \
--to=trast@student$(echo .)ethz.ch \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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