From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v1.8.5-rc0
Date: Fri, 1 Nov 2013 04:52:56 -0400 [thread overview]
Message-ID: <20131101085256.GA28637@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqtxfy9zee.fsf@gitster.dls.corp.google.com>
On Wed, Oct 30, 2013 at 03:17:45PM -0700, Junio C Hamano wrote:
> Git v1.8.5 Release Notes (draft)
> ========================
> [...]
> * A packfile that stores the same object more than once is broken and
> will be rejected by "git index-pack" that is run when receiving
> data over the wire.
We ended up scrapping the index-pack patch, in favor of just using the
existing --strict check. So the correct statement is more like '...will
be rejected by "git index-pack --strict"'. But that is not a new
behavior in v1.8.5. :)
We did fix bugs in GIT_USE_LOOKUP related to duplicates in commit
171bdac. That may not be exciting enough to mention in the release
notes, though, as the code is not even used by default.
-Peff
next prev parent reply other threads:[~2013-11-01 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 22:17 [ANNOUNCE] Git v1.8.5-rc0 Junio C Hamano
2013-11-01 8:52 ` Jeff King [this message]
2013-11-01 10:39 ` Duy Nguyen
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=20131101085256.GA28637@sigill.intra.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).