2019-June 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] Proposal: Change how subprojects interact with parent project remotes and add extra configuration, James Ennis
  • [BuildStream] Proposal: Consider adding type hints, Chandan Singh
  • [BuildStream] Committer Policy, Laurence Urhegyi
  • [BuildStream] Cleaning up BuildStream organization on GitLab, Chandan Singh
  • [BuildStream] Subproject fetching, Jürg Billeter
  • [BuildStream] Specifying default dependencies for element kinds, Chandan Singh
  • [BuildStream] A BuildStream fetcher service, Raoul Hidalgo Charman
  • [BuildStream] Call for agenda - monthly irc team meeting - Tuesday 11 June, Laurence Urhegyi
  • Re: [BuildStream] Responsive, but not overly verbose UX - not-in-scheduler, Jonathan Maw
  • [BuildStream] Reboot discussion: bst artifact subcommand group, Tristan Van Berkom
  • [BuildStream] Weekly performance update for the Debian-like project, James Ennis
  • Re: [BuildStream] bst artifact show, James Ennis

  • Mail converted by MHonArc