From: Muhammad Rizki <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH v2 4/8] atom: Small change for fix_utf8_char()
Date: Fri, 21 Oct 2022 17:44:27 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 21/10/2022 15.27, Ammar Faizi wrote:
> On 10/21/22 3:25 PM, Muhammad Rizki wrote:
>> What about this? can you explain what happened? Because I tested it
>> and it has payload.
>
> I didn't investigate this further. Can you print() the text of
> that email before you send it to Telegram and paste it here?
>
The text content that I'm printing out in the send_text_mail() in the
telegram/packages/client.py is:
#ml
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
To: Dylan Yudaken <[email protected]>
Cc: Pavel Begunkov <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>
Cc: io-uring Mailing List <[email protected]>
Cc: Facebook Kernel Team <[email protected]>
Cc: Dylan Yudaken <[email protected]>
Date: Thu, 20 Oct 2022 05:52:08 -0700
Subject: Re: [PATCH liburing v1 1/3] liburing: Clean up
`-Wshorten-64-to-32` warnings from clang
On 10/20/22 5:12 AM, Ammar Faizi wrote:
> On 10/20/22 6:52 PM, Ammar Faizi wrote:
>> From: Dylan Yudaken<[email protected]>
>>
>> liburing has a couple of int shortening issues found by clang. Clean
>> them all. This cleanup is particularly useful for build systems that
>> include these files and run with that error enabled.
>>
>>
Link:https://lore.kernel.org/io-uring/[email protected]
>> Signed-off-by: Dylan Yudaken<[email protected]>
>> Co-authored-by: Ammar Faizi<[email protected]>
>> Signed-off-by: Ammar Faizi<[email protected]>
>
> BTW, before it's too late. I think we should be consistent on the cast
> style:
>
> (type) a
>
> or
>
> (type)a
>
> What do you think?
I tend to prefer (type) a, but sometimes if you have multiple casts
or the lines become too long, I'll do (type)a. I don't think it's
super important in terms of style, as it isn't that prevalent.
--
Jens Axboe
<code>------------------------------------------------------------------------</code>
next prev parent reply other threads:[~2022-10-21 10:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 8:38 [PATCH v2 0/8] Fix some bugs and add some features Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 1/8] discord: Add send_text_mail_interaction() Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 2/8] discord: Add send_patch_mail_interaction() Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 3/8] discord: Add get lore mail slash command Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 4/8] atom: Small change for fix_utf8_char() Muhammad Rizki
2022-10-21 6:53 ` Ammar Faizi
2022-10-21 7:35 ` Muhammad Rizki
2022-10-21 8:25 ` Muhammad Rizki
2022-10-21 8:27 ` Ammar Faizi
2022-10-21 10:44 ` Muhammad Rizki [this message]
2022-10-21 10:50 ` Ammar Faizi
2022-10-21 10:52 ` Muhammad Rizki
2022-10-21 10:54 ` Ammar Faizi
2022-10-21 10:55 ` Muhammad Rizki
2022-10-21 10:57 ` Ammar Faizi
2022-10-21 10:58 ` Muhammad Rizki
2022-10-21 10:57 ` Muhammad Rizki
2022-10-21 11:00 ` Ammar Faizi
2022-10-21 11:12 ` Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 5/8] atom: Improve remove_patch() Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 6/8] atom: add manage_payload() Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 7/8] telegram: Fix get lore command Muhammad Rizki
2022-10-20 8:38 ` [PATCH v2 8/8] atom: Improve extract_body() Muhammad Rizki
2022-10-20 14:23 ` [PATCH v2 0/8] Fix some bugs and add some features Ammar Faizi
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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