Patrik Nordwall a2e5b3f8a4 =per #16542 Don't store sender in PersistentRepr ... * I think it originated from channels, or some idea that the sender should be revived (as good as possible) during replay, but that is pretty useless * It must still be in PersistentRepr for remote serialization * I didn't want to change to the built in sender when looping to the journal because keeping it together with the message makes it easier to do batching (queueing) * adjust tck		2015-06-18 12:46:50 +02:00
..
src	=per #16542 Don't store sender in PersistentRepr	2015-06-18 12:46:50 +02:00
build.sbt	=pro run multi-jvm tests when validating pr	2015-05-28 13:57:50 +03:00