All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Langlois <olivier@trillion01.com>
To: Jens Axboe <axboe@kernel.dk>, Steven Rostedt <rostedt@goodmis.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition
Date: Sun, 20 Jun 2021 15:15:48 -0400	[thread overview]
Message-ID: <473dbbd3376a085df4672a30f86fe8faf8f8254a.camel@trillion01.com> (raw)
In-Reply-To: <902fdad6-4011-07fc-ea0e-5bac4e34d7bc@kernel.dk>

On Wed, 2021-06-16 at 15:33 -0600, Jens Axboe wrote:
> On 6/16/21 3:30 PM, Olivier Langlois wrote:
> > 
> 
> > My take away from all this is that it is very important that my
> > patches
> > do reach the lists and I commit to put the necessary efforts to
> > make
> > that happen.
> 
> Yes. Both for tooling, but also so that non-cc'ed people see it and
> can
> reply.
> 
> > My last email was simply myself starting diagnose where my problem
> > could be outloud.
> > 
> > Steven did mention that he wasn't seeing the Message-Id field in my
> > patch emails. I'm very grateful for this clue!
> > 
> > My main email client is Gnome Evolution (when Message-Id is present
> > in
> > my mails) and I do the following to send out patches:
> > 
> > 1. git format-patch -o ~/patches HEAD^
> > 2. Edit patch file by adding recipients listed by
> > scripts/get_maintainer.pl
> > 3. cat patch_file | msmtp -t -a default
> 
> Why not just use git send-email? That's literally what that is for.
> It's
> what I use to send out patches.
> 
> 
> 
I found my problem. I had to add the option --thread to git format-
patch

as in:
$ git format-patch --thread -o ~/patches HEAD^



  reply	other threads:[~2021-06-20 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <60be7e31.1c69fb81.a8bfb.2e54SMTPIN_ADDED_MISSING@mx.google.com>
2021-06-15  9:48 ` Pavel Begunkov
2021-06-15 21:50   ` Jens Axboe
2021-06-15 23:35     ` Steven Rostedt
2021-06-16 12:49       ` Jens Axboe
2021-06-16 19:00         ` Olivier Langlois
2021-06-16 19:02           ` Jens Axboe
2021-06-16 21:30             ` Olivier Langlois
2021-06-16 21:33               ` Jens Axboe
2021-06-20 19:15                 ` Olivier Langlois [this message]
2021-06-20 20:13                   ` Pavel Begunkov
2021-06-16 13:33     ` Olivier Langlois
2021-06-16 13:43       ` Steven Rostedt
2021-06-16 13:53       ` Pavel Begunkov

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=473dbbd3376a085df4672a30f86fe8faf8f8254a.camel@trillion01.com \
    --to=olivier@trillion01.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --subject='Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.