Go to file
Dave Borowitz b8a120b338 Reread ChangeData in email constructors
Email processing is often kicked off into a background thread, so it
is not safe to use the non-threadsafe accessors of Change. Rework the
ChangeEmail hierarchy so a new ChangeData is created in each
constructor, which ensures data is reread in a background thread. This
is a little slow, particularly as not all emails are sent async, but
is the best way we have of guaranteeing safety. It is also a little
ugly as the destination project/branch need to be passed to a super
constructor, and we can't have a statement creating this new
ChangeData prior to the super call, so the ChangeData needs to be
explicitly created in each leaf type.

Change-Id: Ibc549791e5cb2a23fbc4d7acca96589782757296
2015-04-16 16:52:24 -07:00
2014-12-18 11:16:03 +09:00
2015-04-14 17:23:51 +09:00
2015-04-14 09:08:54 -04:00
2015-03-19 18:35:04 +09:00
2015-04-07 10:52:27 +09:00
2015-04-15 19:00:51 +09:00
2015-04-08 11:39:46 +09:00
2015-03-04 10:59:02 +09:00
2015-03-07 23:03:15 +01:00
2015-03-03 07:12:16 +00:00
2015-04-08 11:40:19 +09:00
2013-11-09 07:45:00 +01:00
2015-04-08 07:50:41 +00:00
2015-03-04 10:59:02 +09:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2015-03-26 16:38:04 +01:00
Description
RETIRED, Gerrit as used by OpenStack
120 MiB