From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] 回复： Re: package: add kmscon
Date: Sat, 3 Apr 2021 15:35:44 +0200 [thread overview]
Message-ID: <20210403133544.GX24043@scaer> (raw)
In-Reply-To: <1GPg4h1y5xBmcMZ8x0COgHaYlDvdbAAaYawHMnsJXWvW4rLTnPX_Z_i8dPMXiGcW3foDWIR0WHEXswAn-Dug5KGFGbGpYZJes-FQke6mgHY=@protonmail.com>
Hello,
On 2021-04-03 13:22 +0000, qblade via buildroot spake thusly:
> The sad thing is that I am using a free email service, which does not
> provide smtp service for free users. I can only send emails through
> the web version. Is there really no other way to send patches?
You could try sending one patch per email:
1. Be sure your commit are complete: titile, commit log, authorship and
your Signed-off-by line, see:
https://buildroot.org/downloads/manual/manual.html#submitting-patches
2. prepare your patches with git format-patch
3. send the first patch as attachment to the first mail, then the
second patch as attachment to the second mail; make the mail subject
(and body?) duplicate the commit title and commit log.
If all goes well, your patches should popup after a little while on the
list of pending ptches:
https://patchwork.ozlabs.org/project/buildroot/list/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-04-03 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 10:16 [Buildroot] package: add kmscon qblade
2021-04-03 12:18 ` Thomas Petazzoni
2021-04-03 13:22 ` [Buildroot] 回复： " qblade
2021-04-03 13:35 ` Yann E. MORIN [this message]
2021-04-03 13:47 ` qblade
2021-04-03 14:21 ` qblade
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=20210403133544.GX24043@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox