On Mon, Feb 24, 2025 at 05:58:39PM +0400, George Moussalem wrote: > On 2/24/25 17:49, Krzysztof Kozlowski wrote: > > > On 24/02/2025 14:42, Dmitry Baryshkov wrote: > >> On Mon, Feb 24, 2025 at 10:19:35AM +0100, Krzysztof Kozlowski wrote: > >>> On 24/02/2025 07:12, George Moussalem wrote: > >>>> From: Sricharan Ramabadhran <quic_srichara@xxxxxxxxxxx> > >>>> > >>>> Document the QFPROM block found on IPQ5018 > >>>> > >>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> > >>>> Signed-off-by: Sricharan Ramabadhran <quic_srichara@xxxxxxxxxxx> > >>>> Signed-off-by: George Moussalem <george.moussalem@xxxxxxxxxxx> > >>> You can send the patches to yourself and see whether they are properly > >>> threaded. > >> I don't think outlook world understands the concept of threading. > > using git send-email from an @outlook.com address. But I've figured out the issue: > git send-email --thread > this sets In-reply-to and References tags It does that by default. The usual way is to have your cover letter as 0000-foo-bar.patch and then use git send-email 00*. This way it picks up the cover letter as the first patch and everything else goes as reponses to it. OR you can use a tool which does that for you. We usually recommend b4 tool, it wraps ardoung git-send-email and it can help a lot. > > > True, but note that outlook.com is just provider and you can use > > whatever email client with it. mutt/neomutt, Thunderbird, claws, Kmail etc. > > correct, not sending from outlook, but git send-email. Was missing the --thread option > > > Best regards, > > Krzysztof > > Best regards, > George > -- With best wishes Dmitry
