All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zev Weiss <zweiss@equinix.com>
To: Sandeep Kumar <sandeep.pkumar@tcs.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: OpenBmc contribution
Date: Wed, 9 Nov 2022 07:22:22 +0000	[thread overview]
Message-ID: <20221109072156.GD18848@packtop> (raw)
In-Reply-To: <MA1PR01MB4129D8BE91CB235EA9FF6BB1873E9@MA1PR01MB4129.INDPRD01.PROD.OUTLOOK.COM>

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@lists.ozlabs.org> On Behalf Of Sandeep Kumar
>Sent: Tuesday, November 8, 2022 5:30 PM
>To: openbmc@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

  reply	other threads:[~2022-11-09  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 11:59 OpenBmc contribution Sandeep Kumar
2022-11-09  6:28 ` Sandeep Kumar
2022-11-09  7:22   ` Zev Weiss [this message]
2022-11-09  8:11     ` Sandeep Kumar

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=20221109072156.GD18848@packtop \
    --to=zweiss@equinix.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sandeep.pkumar@tcs.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.