From: Stewart Smith <stewart@linux.ibm.com>
To: Sai Dasari <sdasari@fb.com>, Oskar Senft <osk@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"bradleyb\@fuzziesquirrel.com" <bradleyb@fuzziesquirrel.com>,
"gmills\@linux.vnet.ibm.com" <gmills@linux.vnet.ibm.com>
Subject: Re: Submit board schematics to OpenBMC docs repo
Date: Mon, 19 Nov 2018 16:48:42 +1100 [thread overview]
Message-ID: <87ftvxpqh1.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <2A161BFC-87CF-4FE9-9DC5-FF1712EE955C@fb.com>
Sai Dasari <sdasari@fb.com> writes:
> I guess this is a question of # of small repos vs a single large repo with a lot of "stuff" in it. I generally prefer fewer (yet larger) repos vs. the overhead of managing multiple small repos.
> May be an example would clarify for my suggestion of embedding details with the machine. I was referring to having ‘witherspooon’ schematics along with the machine layer @ https://github.com/openbmc/openbmc/tree/master/meta-ibm/meta-witherspoon. This will provide context for how this machine witherspoon is designed with all the details.(hypothetical assuming witherspoon schematics can be shared in open)
Your mail client appears broken and is failing to quote replies correctly.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-11-19 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 19:58 Submit board schematics to OpenBMC docs repo Oskar Senft
2018-11-16 20:10 ` Andrew Luke Nesbit
2018-11-16 21:05 ` Oskar Senft
2018-11-16 20:58 ` Sai Dasari
2018-11-16 21:07 ` Oskar Senft
2018-11-16 22:27 ` Sai Dasari
2018-11-19 5:48 ` Stewart Smith [this message]
2018-11-19 17:31 ` Sai Dasari
2018-11-19 17:34 ` Oskar Senft
2018-11-19 22:01 ` Sai Dasari
2018-11-16 22:26 ` Ed Tanous
2018-11-26 18:57 ` Brad Bishop
2018-11-27 19:57 ` Sai Dasari
2018-11-27 20:51 ` Oskar Senft
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=87ftvxpqh1.fsf@linux.vnet.ibm.com \
--to=stewart@linux.ibm.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=osk@google.com \
--cc=sdasari@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.