2019-April Archive by Thread

Messages are ordered newest-to-oldest in this index. The newest threads will be at the top of this page, the oldest will be at the bottom.

Within a single thread, the first mail note is the START of the thread; the notes following that are in the chronological order of when they were received. So globally, newest messages are at the top, but within a thread, the oldest (the start of the thread) is at the top.

If you think about it, it is confusing. Just go with the flow and everything will be all right.

  • [BuildStream] BuildStream 1.2.6 released, Tristan Van Berkom
  • [BuildStream] BuildStream on Windows, Angelos Evripiotis
  • [BuildStream] Responsive, but not overly verbose UX - not-in-scheduler, Daniel Silverstone
  • [BuildStream] Weekly performance update for the Debian-like project, James Ennis
  • [BuildStream] Partial local CAS for remote execution - next steps, Jürg Billeter
  • [BuildStream] Performance results, April 2019 - Let's discuss options..., Daniel Silverstone
  • [BuildStream] [Proposal] Plugin fragmentation / Treating Plugins as Sources, Tristan Van Berkom
  • [BuildStream] How to synchronize nested junctions, Chandan Singh
  • [BuildStream] Call for agenda - monthly irc team meeting - Tuesday 16 April, Laurence Urhegyi
  • [BuildStream] Weekly performance update - with link to interactive notebooks, James Ennis
  • Re: [BuildStream] Clean separation of BuildStream 1 & 2, Benjamin Schubert
  • Re: [BuildStream] Monthly irc team meeting minutes - Tuesday 19 March 2019, Tristan Van Berkom
  • [BuildStream] Weekly performance update - Regenerated data for a different project, James Ennis
  • [BuildStream] Proposal: Reduce the amount of work that's done at places where we call Element._update_state(), Jonathan Maw

  • Mail converted by MHonArc