What's not in 'master', and likely not to be in, until 1.5.4

Here is an update to the list I sent earlier.

Topics that I thought may deserve attention, discussion and eventual inclusion but are not 1.5.4 material.

I think these two could be part of 1.5.4, but I left them out of 1.5.4-rc4 (IOW, I do not think they should be on this list):

 * marking output from "diff --{no,src,dst}-prefix" as a non-git
   diff (me)

   Linus had an objection but I think I made a reasonable
   argument against that.  Haven't heard back since then, so
   this is in limbo.

 * submodule subcommand parser fix for "git submodule add init
   update" (Imran M Yousuf and me)

   As Jakub noticed, this is meant to be a bugfix but as I do
   not use submodule heavily myself, backing it with real-world
   success stories would be needed.

Now these two out of our way, here is the list.

 * various lstat(2) reduction changes (me, Linus and Dscho).

   This will be queued in 'pu'; it appears this introduces a
   timing related breakages in t75?? tests.

 * compress/decompress abstraction (Marco)

 * crlf (Steffen Prohaska and Dmitry Potapov)

 * whitespace error: "cr at eol is ok" (me)

 * submodule recursive wrapper (Imran M Yousuf)

 * 'origin' is not so special after "clone -o frotz" (Mark Levedahl)

 * "submodule summary" (Ping Yin)

 * unconfigured ident safety (Stephen Sinclair)

 * gitweb feed from commit to commitdiff (Florian La Rouche --
   Jakub seems to be on top of this so I am not worried about it
   too much).

 * color.ui (Matthias Kestenholz)

 * test scripts to use valgrind (Jeff King)

 * "rebase -i" UI -- should it be simplified to do commit --amend
   itself? (Dscho)

 * "cherry-pick/revert" error message fix (Björn Steinbrink and me)

 * pathname safety on filesystems whose readdir(3) thinks it
   knows better than users (Linus, Robin Rosenberg, me and
   others).

   I tend to prefer a much simpler approach Linus suggested, to
   wrap readdir(3) on systems that are known to mangle files,
   but I have a slight suspicion it would not work well enough
   for cross platform projects.

Again, I am hoping that authors will resend the ones they really care about after 1.5.4, as I do not want to take patches early.

The previous version of this list did not include the some that were discussed and landed in 'pu' (or 'offcuts'). The ones that we may want to polish that are in 'pu' are:

 * omit cc recipients from send-email (David Brown)

 * sha1 lookup optimization (me)

 * rewrite cherry-pick/revert in order to improve its D/F
   conflict resolution (me)

 * allow native protocol to tell exactly which branch HEAD
   points at (me)

There is also 1.6.0 material queued already, way before the rc cycle:

 * Moving "git-foo" out of users' $PATH (Nguyễn Thái Ngọc Duy)

I suspect it might be a good idea to make an early declaration that 1.5.5 is to resolve the above listed issues plus the ones already in 'pu' (and nothing else), and have a fairly short cycle after 1.5.4.