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 (Mar 2013, #07; Tue, 26)
Date: Wed, 27 Mar 2013 16:35:35 -0400 [thread overview]
Message-ID: <20130327203535.GA5220@sigill.intra.peff.net> (raw)
In-Reply-To: <7v620dss3j.fsf@alter.siamese.dyndns.org>
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.
> * jk/pkt-line-cleanup (2013-03-21) 20 commits
> - do not use GIT_TRACE_PACKET=3 in tests
> - remote-curl: always parse incoming refs
> - remote-curl: move ref-parsing code up in file
> - remote-curl: pass buffer straight to get_remote_heads
> - teach get_remote_heads to read from a memory buffer
> - pkt-line: share buffer/descriptor reading implementation
> - pkt-line: provide a LARGE_PACKET_MAX static buffer
> - pkt-line: move LARGE_PACKET_MAX definition from sideband
> - pkt-line: teach packet_read_line to chomp newlines
> - pkt-line: provide a generic reading function with options
> - pkt-line: drop safe_write function
> - pkt-line: move a misplaced comment
> - write_or_die: raise SIGPIPE when we get EPIPE
> - upload-archive: use argv_array to store client arguments
> - upload-archive: do not copy repo name
> - send-pack: prefer prefixcmp over memcmp in receive_status
> - fetch-pack: fix out-of-bounds buffer offset in get_ack
> - upload-pack: remove packet debugging harness
> - upload-pack: do not add duplicate objects to shallow list
> - upload-pack: use get_sha1_hex to parse "shallow" lines
>
> Cleans up pkt-line API, implementation and its callers to make them
> more robust. Even though I think this change is correct, please
> report immediately if you find any unintended side effect.
>
> Will merge to 'master' in the 3rd batch (Risky).
I was kind of surprised to see this still in pu, too. I thought it was
supposed to cook in next for a while to shake out any interoperability
bugs (and it was in next previously). Did it get ejected after the
release and then never put back?
-Peff
PS I notice John Keeping has become quite active these days, and has
stolen my initials. It makes searching for my topics in "What's
Cooking" much harder (I read it linearly, but I take special notice
of the "jk" topics).
next prev parent reply other threads:[~2013-03-27 20:36 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 [this message]
2013-03-27 20:50 ` Junio C Hamano
2013-03-27 20:52 ` Jeff King
2013-03-27 20:50 ` Thomas Rast
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
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=20130327203535.GA5220@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.
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).