Submitting patches

[Tudor.Ambarus at microchip.com]

On 8/4/22 09:24, Martin Bonner wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Wed, 3 Aug 2022 at 19:14, Simon Glass <sjg at chromium.org> wrote:
> 
>> Hi Martin,
>>
>> On Wed, 3 Aug 2022 at 04:05, Martin Bonner <martingreybeard at gmail.com>
>> wrote:
>>>
>>> I and my colleagues have a number of patches we would like to
>>> contribute back to the community, however for various reasons
>>> (principally operating inside corporate firewalls), it isn't possible
>>> to use `git send-email`, and I haven't been able to create a plain
>>> text email which is acceptable to `git am`.
>>
>> The workaround here is perhaps to create a gmail address for
>> submissions. I think quite a few people do that.
> 
> Interesting.  I am using gmail (because I assumed that the corporate email
> would mangle stuff), but I can't get it to work.

bypass the company network as well if you can. Try disconnecting the VPN if
you're working from home, or use your phone as a personal hotspot.

> 
> Surprisingly, I think that Office365 email is actually _more_ compliant
> with the way the u-boot process works.
> 
> But a firewall that
>> blocks 'git send-email' is not really compatible with open source
>> collaboration, so I'd encourage you to get the problem resolved.
>>
> 
> That's completely impossible.  Corporate IT will let us push patches

:)

> upstream if we like, but they absolutely are not going to change their
> policies and infrastructure to let that happen.

If I got tired of fighting them, I would bypass the company's infrastructure.