git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2014, #02; Tue, 9)
Date: Tue, 9 Sep 2014 18:20:54 -0400	[thread overview]
Message-ID: <20140909222054.GC14029@peff.net> (raw)
In-Reply-To: <xmqqa968jxj5.fsf@gitster.dls.corp.google.com>

On Tue, Sep 09, 2014 at 02:26:22PM -0700, Junio C Hamano wrote:

> * jk/command-line-config-empty-string (2014-08-05) 1 commit
>   (merged to 'next' on 2014-08-29 at 74f04af)
>  + config: teach "git -c" to recognize an empty string
> 
>  "git -c section.var command" and "git -c section.var= command"
>  should pass the configuration differently (the former should be
>  a boolean true, the latter should be an empty string).

Hmm, there is something funny about the authorship on the sole commit in
that topic. It's too late to fix now (and I do not care too much), but
you may want to puzzle out what happened (stray --reset-author, weird
use of "git am"?).

> * jk/index-pack-threading-races (2014-08-29) 1 commit
>  - index-pack: fix race condition with duplicate bases
> 
>  When receiving an invalid pack stream that records the same object
>  twice, multiple threads got confused due to a race.  We should
>  reject or correct such a stream upon receiving, but that will be a
>  larger change.
> 
>  Will merge to 'next'.

I have been meaning to revisit this topic since the earlier discussion.
At the very least, we need to improve the error message for this case. I
think it's OK to merge this first patch, though, as anything else can
build on it.

-Peff

  reply	other threads:[~2014-09-09 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 21:26 What's cooking in git.git (Sep 2014, #02; Tue, 9) Junio C Hamano
2014-09-09 22:20 ` Jeff King [this message]
2014-09-10 16:39   ` 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=20140909222054.GC14029@peff.net \
    --to=peff@peff.net \
    --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;
as well as URLs for NNTP newsgroup(s).