These patches are in my git tree. Unfortunately since they break builds with shared library enabled, I didn't want to merge them into the primary master or next branches just yet. So I've resurrected something which we haven't used for a while, which is the "proposed updates", or pu branch. The pu branch is a rewinding branch, like linux-next[1], so developers should not try to base any of their branches on it. It's there so people can see what is "on deck" for merging into the next branch. In my internal tree I have one or more topic branches (in this case, it's "vp/json-dumpe2fs") which get merged into the pu branch, which is based off of the next branch when I rebuild it. [1] https://www.kernel.org/doc/man-pages/linux-next.html The pu branch is based on the workflow[2] used by the git developers. [2] https://git-scm.com/docs/gitworkflows See my other e-mail about my proposal regarding moving the json support functions to libe2p and what that would require/imply. - Ted
