-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: |> What's the end result then, we need both patches in to get good |> behaviour all around or Holger's covered it already? | | As far as I can see, Holger's covers the problem I fixed as well.
Holger you have got good stuff in your tree -- more coming -- but I don't know when I should be triggered to take it. I don't want to just directly pick it off your tree either and make those decisions alone. And unless it is part of a dependent patchset it doesn't make sense for someone else to post your patches to the list. Maybe when you think a patch is complete, you can post it here, this alerts everyone to what is being done and triggers it moving on. By all means post you recent patches that went into "andy" here too so everyone can sync up on what goes on. Also I just been tidying up metadata on mokopatches because we want to make a stable history branch. If you have any advice on git methodology for that it's welcome. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkf2CigACgkQOjLpvpq7dMqabQCfcs0RMO81vUr78OLv+btpxFW+ ZxEAn3PKFJQqn8KHOovSnUiW568ApGdR =jW1D -----END PGP SIGNATURE-----
