From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Short-term plans for the post 2.9 cycle
Date: Sun, 19 Jun 2016 15:52:04 -0700 [thread overview]
Message-ID: <xmqqh9covlkb.fsf@gitster.mtv.corp.google.com> (raw)
Here are the list of topics that are in the "private edition" I use
for every day work, grouped by where they sit in the the near-term
plan of merging them up to 'next' and then to 'master'.
These will be merged to 'master' soonish.
ew/fast-import-unpack-limit
ah/no-verify-signature-with-pull-rebase
ew/daemon-socket-keepalive
sb/submodule-misc-cleanups
sb/submodule-recommend-shallowness
et/pretty-format-c-auto
jg/dash-is-last-branch-in-worktree-add
aq/upload-pack-use-parse-options
jc/clear-pathspec
wd/userdiff-css
jk/rev-list-count-with-bitmap
rs/xdiff-hunk-with-func-line
These will be in 'next' immediately after the above gets merged to
'master'.
cc/apply-introduce-state
These have been in 'next', but will be kicked back to give them
chance to clean up when 'next' is rewound.
mh/split-under-lock
mh/ref-iterators
jc/attr
sb/pathspec-label
These are expected to be merged to 'next' in the first batch after
'next' gets rewound.
pc/occurred
tr/doc-tt
ap/git-svn-propset-doc
jk/fetch-prune-doc
dn/gpg-doc
pb/strbuf-read-file-doc
lf/receive-pack-auto-gc-to-client
mg/cherry-pick-multi-on-unborn
sg/reflog-past-root
vs/prompt-avoid-unset-variable
rj/compat-regex-size-max-fix
jk/avoid-unbounded-alloca
et/add-chmod-x
jc/deref-tag
nb/gnome-keyring-build
lv/status-say-working-tree-not-directory
tb/complete-status
em/newer-freebsd-shells-are-fine-with-returns
These are the second batch for 'next'.
km/fetch-do-not-free-remote-name
jk/parseopt-string-list
jk/string-list-static-init
lf/sideband-returns-void
jk/bisect-show-tree
jk/add-i-diff-compact-heuristics
jk/big-and-future-archive-tar
jk/send-pack-stdio
lf/recv-sideband-cleanup
pb/commit-editmsg-path
nd/test-lib-httpd-show-error-log-in-verbose
ep/http-curl-trace
These are the third batch.
mh/connect
ew/mboxrd-format-am
jk/repack-keep-unreachable
jk/gpg-interface-cleanup
sb/submodule-clone-retry
mg/signature-doc
These are the fourth.
nd/worktree-cleanup-post-head-protection
jk/upload-pack-hook
nd/graph-width-padded
nd/shallow-deepen
sb/submodule-default-paths
nd/worktree-lock
These are the remainder.
jc/blame-reverse
jc/send-email-skip-backup
va/i18n-even-more
dt/index-helper
dk/blame-move-no-reason-for-1-line-context
sb/clone-shallow-passthru
Some of them that are regression fixes may need to jump the queue
and land on 'master' earlier than others.
next reply other threads:[~2016-06-19 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 22:52 Junio C Hamano [this message]
2016-06-20 16:46 ` Short-term plans for the post 2.9 cycle Stefan Beller
2016-06-20 17:05 ` Junio C Hamano
2016-06-24 15:48 ` Jeff King
2016-06-24 16:54 ` Junio C Hamano
2016-06-24 17:21 ` 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=xmqqh9covlkb.fsf@gitster.mtv.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.
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).