OpenBmc contribution

Sandeep Kumar sandeep.pkumar at tcs.com
Wed Nov 9 19:11:34 AEDT 2022


 TCS Confidential

Hi Zev,

I will keep that in mind. Thanks for the info .

Thanks,
Sandeep. 


 TCS Confidential

-----Original Message-----
From: openbmc <openbmc-bounces+sandeep.pkumar=tcs.com at lists.ozlabs.org> On Behalf Of Zev Weiss
Sent: Wednesday, November 9, 2022 12:52 PM
To: Sandeep Kumar <sandeep.pkumar at tcs.com>
Cc: openbmc at lists.ozlabs.org
Subject: Re: OpenBmc contribution

"External email. Open with Caution"

On Tue, Nov 08, 2022 at 10:28:01PM PST, Sandeep Kumar wrote:
>TCS Confidential
>
>Hi,
>
>Any input on the below query?
>
>Thanks,
>Sandeep.
>
>
>
>TCS Confidential
>From: openbmc <openbmc-bounces+sandeep.pkumar=tcs.com at lists.ozlabs.org> 
>On Behalf Of Sandeep Kumar
>Sent: Tuesday, November 8, 2022 5:30 PM
>To: openbmc at lists.ozlabs.org
>Subject: OpenBmc contribution
>
>"External email. Open with Caution"
>
>TCS Confidential
>
>Hi All,
>
>Is it okay to submit our changes with testing done on a qemu?
>
>Thanks,
>Sandeep.
>
>
>TCS Confidential
>

Hi Sandeep,

Bear in mind that people working on OpenBMC are in many different time zones around the world (and are often generally busy themselves) -- as a matter of etiquette I'd suggest waiting a bit more than 18 hours before following up to prod the list for a response.

To address your question, I'm not aware of any project-wide rules on that, so I'd guess it probably depends on (a) the nature of the patch in question, and (b) the judgement of the maintainer(s) of the repo you're working on.  Feel free to post a patch to gerrit with a description of the testing you've done; if the maintainers feel your testing is insufficient for your patch they'll let you know.


Zev
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you





More information about the openbmc mailing list