To: git@vger.kernel.org
-Subject: What's cooking in git.git (Aug 2012, #03; Mon, 13)
+Bcc: lwn@lwn.net
+Subject: What's cooking in git.git (Aug 2012, #04; Tue, 14)
X-master-at: 61b472ed8b090a3e9240590c85041120a54dd268
X-next-at: 4accbf693d5564e36b727349eebdbcb0d4f70a02
-What's cooking in git.git (Aug 2012, #03; Mon, 13)
+What's cooking in git.git (Aug 2012, #04; Tue, 14)
--------------------------------------------------
Here are the topics that have been cooking. Commits prefixed with '-' are
only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'.
+Hopefully tomorrow's 1.7.12-rc3 will be the final rc before the real
+thing.
+
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"]
-
-* bw/maint-1.7.9-solaris-getpass (2012-08-06) 2 commits
- (merged to 'next' on 2012-08-07 at d78bc37)
- + Enable HAVE_DEV_TTY for Solaris
- + terminal: seek when switching between reading and writing
-
-The recent update to terminal I/O interface to get passwords &c
-interactively didn't quite work on Solaris.
-
--------------------------------------------------
[New Topics]
-* bc/receive-pack-stdout-protection (2012-08-06) 2 commits
- (merged to 'next' on 2012-08-07 at d7aa316)
- + receive-pack: do not leak output from auto-gc to standard output
- + t/t5400: demonstrate breakage caused by informational message from prune
-
-When "git push" triggered the automatic gc on the receiving end, a
-message from "git prune" that said it was removing cruft leaked to
-the standard output, breaking the communication protocol.
-
-Not urgent (non regression).
-
-* bc/prune-info (2012-08-07) 1 commit
- - prune.c: only print informational message in show_only or verbose mode
-
-Teach "git prune" without "-v" to be silent about leftover temporary files.
-
-Not urgent (non regression).
-
-* jc/tag-doc (2012-08-06) 1 commit
- - Documentation: do not mention .git/refs/* directories
-
-Our documentation used to assume having files in .git/refs/*
-directories was the only to have branches and tags, but that is not
-true for quite some time.
-
-Not urgent (non regression).
-
-* jk/docs-docbook-monospace-display (2012-08-07) 1 commit
- - docs: monospace listings in docbook output
-
-The documentation in the TeXinfo format was using indented output
-for materials meant to be examples that are better typeset in
-monospace.
-
-Not urgent (non regression).
-
-* jc/maint-protect-sh-from-ifs (2012-08-08) 1 commit
- - sh-setup: protect from exported IFS
-
-When the user exports a non-default IFS without HT, scripts that
-rely on being able to parse "ls-files -s | while read a b c..."
-start to fail. Protect them from such a misconfiguration.
-
-* jk/check-docs-update (2012-08-08) 8 commits
- - check-docs: get documented command list from Makefile
- - check-docs: drop git-help special-case
- - check-docs: list git-gui as a command
- - check-docs: factor out command-list
- - command-list: mention git-credential-* helpers
- - command-list: add git-sh-i18n
- - check-docs: update non-command documentation list
- - check-docs: mention gitweb specially
-
-Simplify "make check-docs" implementation and update its coverage.
-
-* js/gitweb-path-info-unquote (2012-08-09) 1 commit
- - gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO
-
-Stripping of PATH_INFO in gitweb did not take url style quoting into
-account, failing to notice directories with funny characters e.g. SP
-in their paths.
+* hv/submodule-path-unmatch (2012-08-14) 1 commit
+ - Let submodule command exit with error status if path does not exist
-* mg/rebase-i-onto-reflog-in-full (2012-08-10) 1 commit
- - rebase -i: use full onto sha1 in reflog
+As the title says.
-The reflog entries left by "git rebase" and "git rebase -i" were
-inconsistent.
+* jc/add-delete-default (2012-08-13) 1 commit
+ - git add: notice removal of tracked paths by default
-* mz/empty-rebase-test (2012-08-09) 1 commit
- - add tests for 'git rebase --keep-empty'
+"git add dir/" updated modified files and added new files, but does
+not notice removed files, which may be "Huh?" to some users. They
+can of course use "git add -A dir/", but why should they?
-* jc/capabilities (2012-08-10) 1 commit
- - fetch-pack: do not ask for unadvertised capabilities
- (this branch uses jk/version-string.)
+* jc/maint-rev-list-topo-doc (2012-08-13) 1 commit
+ - rev-list docs: clarify --topo-order description
-Some capabilities were asked by fetch-pack even when upload-pack did
-not advertise that they are available. Fix fetch-pack not to do so.
-
-May have to be rebased to older maintenance tracks before moving
-forward.
-
-* pw/p4-use-client-spec-branch-detection (2012-08-11) 5 commits
- - git p4: make branch detection work with --use-client-spec
- - git p4: do wildcard decoding in stripRepoPath
- - git p4: set self.branchPrefixes in initialization
- - git p4 test: add broken --use-client-spec --detect-branches tests
- - git p4 test: move client_view() function to library
+Further rewording suggestions by Martin and Thomas were good, but
+haven't been incorporated into this patch.
--------------------------------------------------
[Stalled]
--------------------------------------------------
[Cooking]
+* bc/receive-pack-stdout-protection (2012-08-06) 2 commits
+ (merged to 'next' on 2012-08-07 at d7aa316)
+ + receive-pack: do not leak output from auto-gc to standard output
+ + t/t5400: demonstrate breakage caused by informational message from prune
+
+When "git push" triggered the automatic gc on the receiving end, a
+message from "git prune" that said it was removing cruft leaked to
+the standard output, breaking the communication protocol.
+
+Not urgent (non regression).
+
+* bc/prune-info (2012-08-07) 1 commit
+ - prune.c: only print informational message in show_only or verbose mode
+
+Teach "git prune" without "-v" to be silent about leftover temporary files.
+
+Not urgent (non regression).
+
+* jc/tag-doc (2012-08-06) 1 commit
+ - Documentation: do not mention .git/refs/* directories
+
+Our documentation used to assume having files in .git/refs/*
+directories was the only to have branches and tags, but that is not
+true for quite some time.
+
+Not urgent (non regression).
+
+* jk/docs-docbook-monospace-display (2012-08-07) 1 commit
+ - docs: monospace listings in docbook output
+
+The documentation in the TeXinfo format was using indented output
+for materials meant to be examples that are better typeset in
+monospace.
+
+Not urgent (non regression).
+
+* jc/maint-protect-sh-from-ifs (2012-08-08) 1 commit
+ - sh-setup: protect from exported IFS
+
+When the user exports a non-default IFS without HT, scripts that
+rely on being able to parse "ls-files -s | while read a b c..."
+start to fail. Protect them from such a misconfiguration.
+
+* jk/check-docs-update (2012-08-08) 8 commits
+ - check-docs: get documented command list from Makefile
+ - check-docs: drop git-help special-case
+ - check-docs: list git-gui as a command
+ - check-docs: factor out command-list
+ - command-list: mention git-credential-* helpers
+ - command-list: add git-sh-i18n
+ - check-docs: update non-command documentation list
+ - check-docs: mention gitweb specially
+
+Simplify "make check-docs" implementation and update its coverage.
+
+* js/gitweb-path-info-unquote (2012-08-09) 1 commit
+ - gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO
+
+Stripping of PATH_INFO in gitweb did not take url style quoting into
+account, failing to notice directories with funny characters e.g. SP
+in their paths.
+
+* mg/rebase-i-onto-reflog-in-full (2012-08-10) 1 commit
+ - rebase -i: use full onto sha1 in reflog
+
+The reflog entries left by "git rebase" and "git rebase -i" were
+inconsistent.
+
+* mz/empty-rebase-test (2012-08-09) 1 commit
+ - add tests for 'git rebase --keep-empty'
+
+* jc/capabilities (2012-08-13) 3 commits
+ - fetch-pack: mention server version with verbose output
+ - parse_feature_request: make it easier to see feature values
+ - fetch-pack: do not ask for unadvertised capabilities
+ (this branch uses jk/version-string.)
+
+Some capabilities were asked by fetch-pack even when upload-pack did
+not advertise that they are available. Fix fetch-pack not to do so.
+
+* pw/p4-use-client-spec-branch-detection (2012-08-11) 5 commits
+ - git p4: make branch detection work with --use-client-spec
+ - git p4: do wildcard decoding in stripRepoPath
+ - git p4: set self.branchPrefixes in initialization
+ - git p4 test: add broken --use-client-spec --detect-branches tests
+ - git p4 test: move client_view() function to library
+
* jc/maint-push-refs-all (2012-08-07) 2 commits
- get_fetch_map(): tighten checks on dest refs
- fetch/push: allow refs/*:refs/*