From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's cooking (interim report)
Date: Tue, 08 Jan 2013 16:53:19 -0800 [thread overview]
Message-ID: <7vtxqr9ny8.fsf@alter.siamese.dyndns.org> (raw)
I'll do the next issue of "What's cooking" after tomorrow's
integration cycle, but here are the highlights.
The following topics that have already graduated to the 'master'
branch have been merged to the 'maint' branch (see the last "What's
cooking" for details of individual topics):
ms/subtree-fixlets
ss/nedmalloc-compilation
jc/maint-fnmatch-old-style-definition
jc/test-portability
jc/maint-fbsd-sh-ifs-workaround
jc/mkstemp-more-careful-error-reporting
jc/test-cvs-no-init-in-existing-dir
jc/maint-test-portability
In addition, the following two patches have been directly applied to
the 'maint' branch:
t1402: work around shell quoting issue on NetBSD
remote-hg: Fix biridectionality -> bidirectionality typos
We will have other bugfix topics merged to 'maint' and hopefully can
tag v1.8.1.1 sometime next week.
The following topics that have been cooking on 'next' have been
merged to the 'master' branch:
kb/maint-bundle-doc
as/test-name-alias-uniquely
ta/remove-stale-translated-tut
tb/test-t9810-no-sed-i
tb/test-t9020-no-which
jk/maint-fast-import-doc-dedup-done
jk/pathspec-literal
Most of these will later be merged to 'maint'.
These topics have been merged to the 'next' branch:
rs/zip-with-uncompressed-size-in-the-header
rs/zip-tests
jn/xml-depends-on-asciidoc-conf
jc/comment-cygwin-win32api-in-makefile
as/api-allocation-doc
jk/unify-exit-code-by-receiving-signal
rs/leave-base-name-in-name-field-of-tar
jl/interrupt-clone-remove-separate-git-dir
jc/merge-blobs
mo/cvs-server-updates
as/dir-c-cleanup
jk/config-uname
Also several new topics are parked in 'pu' and I think they are all
ready for 'next'.
Thanks.
next reply other threads:[~2013-01-09 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 0:53 Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-03 23:06 What's cooking (interim report) Junio C Hamano
2016-08-03 23:12 ` Stefan Beller
2016-08-04 2:46 ` Jeff King
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=7vtxqr9ny8.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).