From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.1.2] (unknown [101.128.125.123]) by gnuweeb.org (Postfix) with ESMTPSA id 9DCF4804D1; Fri, 21 Oct 2022 10:44:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1666349071; bh=eBfUNnA9NjvzsmLWM9HcF2Tx+fPDjIZMk4txRXDtvZ8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=o6tm62SmFJoCmygf9Ls6zt52lt8qno5DYWfj+aslZjnNaCBWILQEdnrD1O/rVK4CT +2xwDkHnZYVOXhapDIOPiue5y0fuNmqBHc9ksWyt2FQryUM7K0TqgrnG3Q8o1mtGFI 0RfYACXMH5vbOd4f217orQKupCmjSS8pOYnWHv5hpl3T5+tO1P9FbNdtAGF7KBdqmD zB8Ow5jBN8RVL9fu4Sv9O97iERY/UlG+DW3NUCCR3x4UrtdhDk+fxlU9IUkYTK1Nt/ CYjh1uXnCoBmX3uXfX1/EuApSYqolbeXt5eaO9TuY8YfCAyuOJ++P0kS3dMCxGAHNH I7yaJxVm0mjJw== Message-ID: <553365db-106b-dc91-108c-38b3d9b0bbba@gnuweeb.org> Date: Fri, 21 Oct 2022 17:44:27 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3 Subject: Re: [PATCH v2 4/8] atom: Small change for fix_utf8_char() Content-Language: en-US To: Ammar Faizi Cc: Alviro Iskandar Setiawan , GNU/Weeb Mailing List References: <20221020083845.907-1-kiizuha@gnuweeb.org> <20221020083845.907-5-kiizuha@gnuweeb.org> From: Muhammad Rizki In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: 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 To: Ammar Faizi To: Dylan Yudaken Cc: Pavel Begunkov Cc: GNU/Weeb Mailing List Cc: io-uring Mailing List Cc: Facebook Kernel Team Cc: Dylan Yudaken 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 >> >> 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/20221019145042.446477-1-dylany@meta.com >> Signed-off-by: Dylan Yudaken >> Co-authored-by: Ammar Faizi >> Signed-off-by: Ammar Faizi > > 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 ------------------------------------------------------------------------