Upstreaming downstream Google BMC repositories

[Paul Menzel]

Dear Brandon,


Am 07.01.21 um 02:49 schrieb Brandon Kim:

> We're exploring ways of upstreaming some of the downstream repositories
> from Google to openbmc/* .
> 
> Half, if not most of the downstream repositories are C++ daemons that are
> specific to Google so we didn't want to create a bunch of new
> openbmc/<repo> that no one would use.
> 
> An idea that Ed gave me was having something like openbmc/google-misc
> repository for all these repositories and if there are any that seem useful
> to others, we can break it out into a different, separate repository in
> openbmc/* layer.
> 
> Please let me know if this seems like a good idea and I'm open to other
> suggestions!

Thank you very much for putting in the effort to make these repositories 
public.

Using the openbmc/google-misc approach, how would the git history 
(commit log) be handled?

Personally, I would prefer having small repositories as git makes that 
very easy to handle. Also it might save you time, as you do not have to 
think about what to do with the git history, and do not have to merge it.


Kind regards,

Paul