From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81C5AC433DB for ; Thu, 7 Jan 2021 08:10:17 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 21E9123125 for ; Thu, 7 Jan 2021 08:10:15 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 21E9123125 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4DBJnK2BDKzDr7n for ; Thu, 7 Jan 2021 19:10:13 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=molgen.mpg.de (client-ip=141.14.17.11; helo=mx1.molgen.mpg.de; envelope-from=pmenzel@molgen.mpg.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de X-Greylist: delayed 382 seconds by postgrey-1.36 at bilbo; Thu, 07 Jan 2021 19:08:39 AEDT Received: from mx1.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4DBJlW3H28zDqly for ; Thu, 7 Jan 2021 19:08:39 +1100 (AEDT) Received: from [192.168.0.6] (ip5f5aed1c.dynamic.kabel-deutschland.de [95.90.237.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id EBA192064713C; Thu, 7 Jan 2021 09:01:59 +0100 (CET) Subject: Re: Upstreaming downstream Google BMC repositories To: Brandon Kim References: From: Paul Menzel Message-ID: <2e3f9acc-cc58-6f71-2e42-e046109dd5ec@molgen.mpg.de> Date: Thu, 7 Jan 2021 09:01:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: openbmc@lists.ozlabs.org Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" 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/ 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