Em Sat, 1 Feb 2025 09:44:18 +0900 YongSu Yoo <yongsuyoo0215@xxxxxxxxx> escreveu: > Dear Mauro Carvalho Chehab > > I know how to send an E-mail using "....git send-email --to .." > But, > I do not know how to reply to this E-mail loop using "....git send-email > --to .." > Can you kindly guide me ? Never used git send-email to reply, as it is mainly focused on sending e-mails, not being a true emailer: it just sends e-mail: it doesn't receive. In thesis, you could download the original e-mail using b4 or lei, then manually write a reply text on it and use git send-email. This is easier said than done, as you'll need to take care of SMTP headers yourself. This would require some knowledge about SMTP RFCs. If I were you, I would seek for some other alternatives. Most people use mutt for Kernel work, as it is CLI. There is also alpine I haven't used alpine for ages, but it is a decent CLI e-mail client, using a very simple interface, although it has less features than mutt. I prefer instead to use claws-mail as it has a reasonable GUI, it is fast and it is not overbloated with features I won't use. Neither mutt, alpine or claws-mail mangle whitespaces and line breaks on e-mails, and they can be setup to not do top-postings. If you want something simpler, perhaps you could try notmuch[1]. I never tried myself, but I heard it can be used to reply to e-mails without even needing to subscribe to a ML. [1] https://notmuchmail.org/ You may also find useful to have a SMTP relay server. Probably one of the simplest ones to setup is msmtp: https://marlam.de/msmtp/. I hope that helps. Regards, Mauro > > 2024년 5월 31일 (금) 오전 3:31, Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>님이 작성: > > > Em Tue, 28 May 2024 21:14:37 +0900 > > YongSu Yoo <yongsuyoo0215@xxxxxxxxx> escreveu: > > > > > Dear Markus Elfring > > > > Please don't top-post. Makes hard to follow the comments. > > > > > > > > > 2024년 5월 28일 (화) 오후 2:38, Markus Elfring <Markus.Elfring@xxxxxx>님이 작성: > > > > > > > > > > > … > > > > > For preventing this problem from happening, we make CA_RESET ioctl do > > > > > nothing and only return EBUSY if the ioctl is called during the > > > > > "transiting" states. > > > > > > > > Would you like to avoid any typos (in the summary phrase)? > > > > > Initially, I sent this E-mail using the below command > > > "....git send-email --to mchehab@xxxxxxxxxx, > > > linux-media@xxxxxxxxxxxxxxx, xxxxxxxxxxx.patch. ..." > > > > Git send-email is a good way to send patches. You may also use > > a decent e-mail client that won't mangle with whitespaces. I use > > myself claws-mail; other develpers use emacs. Feel free to pick your > > poison, but if the email doesn't handle whitespaces well and/or > > don't allow writing the answers below the original comments (instead > > of top-posting), it shouldn't be used. > > > > > In response to what you suggested, is it OK if I use Gmail and attach > > > a new patch ? > > > > No. Never attach a patch as the mailing list will reject, and if not, > > patchwork.linuxtv.org won't pick it. > > > > You may use gmail, if you setup your e-mail client to use it as a > > SMTP server. Using webmail solutions typically won't work open source > > discussions, as it does lots of wrong things, like top-posting, not > > honoring 80 columns on emails and/or mangling tabs and white spaces. > > > > Thanks, > > Mauro > > Thanks, Mauro
