and '7b7931f18c15ffa3b7afb35470d5d0dfd5714f30'

where available..

     and '7069e4dcedf5578597d00177dd220e02ded3634e'

      under the assumption that they are already talking
      to most of the routers, so there's no reason to reject. This may drive them
      to their conn. limits, but it's hopefully a temporary solution to the
      tunnel build congestion. As the net grows this will have to be revisited.

      to give us more capacity during congestion

      Under the one-packet-enough theory, and the fact that most
      tunnels in a x+1 pool are of length x, variable lengths
      don't really help that much. Also, a default of 1 led
      to all sorts of problems with iMule/SAM, who was not
      setting the variance properties.
      This will affect exploratory tunnels for new users,
      and those that have never saved a change on configtunnels.jsp,
      and iMule users 1.4.5 and earlier.

     and 'd3f05848c1bb55868499e9e7d65fbf878b731f1a'

    * orange flash remove take 2

    * Merge as -7

     and 'e9067362adb090ff1e3d8ae327fb313ded00e9c6'

Remove notes about editing readme*.html, since we're probably going to start including them in the updates

     and 'f232d5bc50d8723d65c9fcb1092ebcb8333a83e4'

            to branch 'i2p.i2p' (head a3189032197fadc3ecba67c5568b8841e8a6105e)

      - Bring back details links for Postman2 B64 torrents

      - Allow NTCP-only peers in inbound tunnels

      - Make reduce-on-idle the default for all the shared clients
        for new installs (15m)

      - Move from a single connection limit threshold (80%) to
        two (75% and 87%), and only start rejecting tunnels
        at the higher threshold, to increase build success
      - Move some limit methods from the transports to TransportImpl
      - Add limit methods with a threshold argument