From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Brad Bishop" <bradleyb@fuzziesquirrel.com>,
"George Liu" <liuxiwei1013@gmail.com>
Cc: Devender Rao <devenrao@in.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Question regarding phosphor-dbus-monitor repo
Date: Fri, 17 Sep 2021 09:25:51 +0930 [thread overview]
Message-ID: <c9ca0c42-880e-48a4-8889-a92fddbd35a5@www.fastmail.com> (raw)
In-Reply-To: <20210916122652.qi553jxvvvhtnkdn@cheese>
On Thu, 16 Sep 2021, at 21:56, Brad Bishop wrote:
> In hindsight, I think it is too abstract and enables too much
> logic implemented with data.
+100
prev parent reply other threads:[~2021-09-16 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 7:24 Question regarding phosphor-dbus-monitor repo George Liu
2021-09-16 12:26 ` Brad Bishop
2021-09-16 18:42 ` John Broadbent
2021-09-16 23:55 ` Andrew Jeffery [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9ca0c42-880e-48a4-8889-a92fddbd35a5@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=bradleyb@fuzziesquirrel.com \
--cc=devenrao@in.ibm.com \
--cc=liuxiwei1013@gmail.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).