Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
As we already have merged enough changes to 'master' during this
cycle that can potentially cause unforseen regressions, let's not
merge topics that are not regression fixes from 'next' to 'master',
either, until the final release.
You can find the changes described here in the integration branches
of the repositories listed at
http://git-blame.blogspot.com/p/git-public-repositories.html
--
[Graduated to master]
* fc/remote-bzr (2013-04-30) 18 commits
- remote-bzr: access branches only when needed
- remote-bzr: delay peer branch usage
- remote-bzr: iterate revisions properly
- remote-bzr: improve progress reporting
- remote-bzr: add option to specify branches
- remote-bzr: add custom method to find branches
- remote-bzr: improve author sanitazion
- remote-bzr: add support for shared repo
- remote-bzr: fix branch names
- remote-bzr: add support for bzr repos
- remote-bzr: use branch variable when appropriate
- remote-bzr: fix partially pushed merge
- remote-bzr: fixes for branch diverge
- remote-bzr: add support to push merges
- remote-bzr: always try to update the worktree
- remote-bzr: fix order of locking in CustomTree
- remote-bzr: delay blob fetching until the very end
- remote-bzr: cleanup CustomTree
To replace the one we pushed out in 1.8.2 after hearing that Emacs
folks had a good experience with this version, this will be in
1.8.3-rc2.
--
[New Topics]
* fc/fast-export-persistent-marks (2013-05-06) 3 commits
- fast-export: don't parse commits while reading marks file
- fast-export: do not parse non-commit objects while reading marks file
- fast-{import,export}: use get_sha1_hex() directly
Seems to break a handful of topics when merged to the tip of 'pu'.
* jc/core-checkstat-2.0 (2013-05-06) 2 commits
- core.statinfo: remove as promised in Git 2.0
- deprecate core.statinfo at Git 2.0 boundary
The bottom one is a fix for a breakage of a new feature in 1.8.2
but it is not all that urgent.
* jk/packed-refs-race (2013-05-06) 4 commits
- for_each_ref: load all loose refs before packed refs
- get_packed_refs: reload packed-refs file when it changes
- add a stat_validity struct
- resolve_ref: close race condition for packed refs
--
[Stalled]
* mg/more-textconv (2013-04-23) 7 commits
- git grep: honor textconv by default
- grep: honor --textconv for the case rev:path
- grep: allow to use textconv filters
- t7008: demonstrate behavior of grep with textconv
- cat-file: do not die on --textconv without textconv filters
- show: honor --textconv for blobs
- t4030: demonstrate behavior of show with textconv
Rerolled. I am not sure if I like show blob and grep that use
textconv by default, though.
* mh/multimail (2013-04-21) 1 commit
- git-multimail: a replacement for post-receive-email
Waiting for comments.
* jc/format-patch (2013-04-22) 2 commits
- format-patch: --inline-single
- format-patch: rename no_inline field
A new option to send a single patch to the standard output to be
appended at the bottom of a message. I personally have no need for
this, but it was easy enough to cobble together. Tests, docs and
stripping out more MIMEy stuff are left as exercises to interested
parties.
Not ready for inclusion.
* jk/gitweb-utf8 (2013-04-08) 4 commits
- gitweb: Fix broken blob action parameters on blob/commitdiff pages
- gitweb: Don't append ';js=(0|1)' to external links
- gitweb: Make feed title valid utf8
- gitweb: Fix utf8 encoding for blob_plain, blobdiff_plain, commitdiff_plain,
and patch
Various fixes to gitweb.
Waiting for a reroll after a review.
* jk/commit-info-slab (2013-04-19) 3 commits
- commit-slab: introduce a macro to define a slab for new type
- commit-slab: avoid large realloc
- commit: allow associating auxiliary info on-demand
(this branch is used by jc/show-branch.)
Technology demonstration to show a way we could use unbound number
of flag bits on commit objects.
* jn/config-ignore-inaccessible (2013-04-15) 1 commit
- config: allow inaccessible configuration under $HOME
When $HOME is misconfigured to point at an unreadable directory, we
used to complain and die. This loosens the check.
I do not think we agreed that this is a good idea, though.
--
[Cooking]
* fc/at-head (2013-05-02) 5 commits
- Add new @ shortcut for HEAD
- sha1_name: refactor reinterpret()
- sha1_name: compare variable with constant, not constant with variable
- sha1_name: remove unnecessary braces
- sha1_name: remove no-op
Instead of typing four capital letters HEAD, you can say @
instead.
There was another series from Ram that looked mostly test updates
but I lost
