From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [FYI] 'next' will be rewound shortly
Date: Mon, 24 Feb 2014 16:33:31 -0800 [thread overview]
Message-ID: <xmqqeh2s6nfo.fsf@gitster.dls.corp.google.com> (raw)
Just a quick heads-up.
As the first wave for the post-1.9.0 development cycle, these topics
will be merged to 'master' (unless there are serious last minute
issues found) shortly:
+ kb/fast-hashmap 02-24/01-03 #18
+ nv/commit-gpgsign-config 02-24/01-03 #3
+ da/pull-ff-configuration 01-15/01-22 #2
+ bk/refresh-missing-ok-in-merge-recursive 02-24/01-29 #4
+ ds/rev-parse-required-args 01-28/01-31 #1
+ jk/config-path-include-fix 01-28/01-31 #2
+ bs/stdio-undef-before-redef 01-31/01-31 #1
+ ep/varscope 01-31/01-31 #7
+ nd/submodule-pathspec-ending-with-slash 02-24/01-31 #8
+ nd/diff-quiet-stat-dirty 02-24/01-31 #2
+ nd/test-rename-reset 02-04/02-06 #1
+ mw/symlinks 02-04/02-06 #6
+ ks/tree-diff-walk 02-24/02-06 #5
+ wk/submodule-on-branch 02-24/02-06 #4
+ nd/reset-intent-to-add 02-05/02-07 #1
+ jk/test-ports 02-10/02-13 #2
+ al/docs 02-11/02-13 #4
+ bc/gpg-sign-everywhere 02-11/02-13 #9
+ jk/pack-bitmap 02-12/02-13 #26
+ nd/http-fetch-shallow-fix 02-13/02-13 #7
+ dk/blame-janitorial 02-24/02-13 #4
and the tip of 'next' will be rewound at the same time (like, say,
tomorrow).
We may want to merge the 2.0.0 transition topics as the second wave
to 'master' (and starting Documentation/RelNotes/2.0.0.txt) before
merging topics other than the above to it.
There are about 30 more topics that are ready for 'next' (not
counting the ones for 2.0.0 transition), all of which are likely to
be in 'next' soonish.
+ nd/daemonize-gc 02-10/02-20 #2
+ jk/run-network-tests-by-default 02-14/02-20 #1
+ ks/combine-diff 02-24/02-20 #6
- jc/check-attr-honor-working-tree 02-06 #2
- nd/gitignore-trailing-whitespace 02-10 #2
- ss/completion-rec-sub-fetch-push 02-11 #1
- jk/http-no-curl-easy 02-18 #1
- jk/janitorial-fixes 02-18 #5
- ks/config-file-stdin 02-18 #4
- lb/contrib-contacts-looser-diff-parsing 02-18 #1
- nd/reset-setup-worktree 02-18 #1
- tr/diff-submodule-no-reuse-worktree 02-18 #1
- ak/gitweb-fit-image 02-20 #1
- mh/replace-refs-variable-rename 02-20 #1
- nd/no-more-fnmatch 02-20 #4
- rt/links-for-asciidoctor 02-20 #1
- jh/note-trees-record-blobs 02-20 #1
- da/difftool-git-files 02-24 #1
- jk/commit-dates-parsing-fix 02-24 #5
- jk/remote-pushremote-config-reading 02-24 #1
- jm/stash-doc-k-for-keep 02-24 #1
- jn/am-doc-hooks 02-24 #1
- mh/object-code-cleanup 02-24 #4
- nd/i18n-progress 02-24 #1
- fc/transport-helper-fixes 02-24 #7
- tg/index-v4-format 02-24 #3
- ks/tree-diff-more 02-24 #15
I may be a bit too busy to be able to pick up new topics for a few
days, as the topic-flipping is usually quite time consuming when
some ordering of the topics change, i.e. when rerere stops to be
helpful.
Thanks.
reply other threads:[~2014-02-25 0:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xmqqeh2s6nfo.fsf@gitster.dls.corp.google.com \
--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.
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).