From: Jonathan Corbet <corbet@lwn.net>
To: Cengiz Can <cengizc@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: update i2c-dev.h warning in documentation
Date: Thu, 21 Dec 2017 13:54:57 -0700 [thread overview]
Message-ID: <20171221135457.0bd71225@lwn.net> (raw)
In-Reply-To: <CANp8-fz5qQpY4xJCexkLzAZE6jXEMhykKARNyY9C5t0cxbZjTQ@mail.gmail.com>
On Thu, 21 Dec 2017 23:49:16 +0300
Cengiz Can <cengizc@gmail.com> wrote:
> I've ditched claws-mail and will use git send-mail instead.
FWIW, I use claws for patch mailing and more. It can be made to work, you
just need to tweak the options a bit. The trick is to send patches to
yourself and keep at it until what you receive still applies.
jon
prev parent reply other threads:[~2017-12-21 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 20:10 [PATCH] i2c: update i2c-dev.h warning in documentation Cengiz Can
2017-12-11 23:20 ` Jonathan Corbet
2017-12-12 16:43 ` [PATCH v2] " Cengiz C.
2017-12-21 19:38 ` Jonathan Corbet
2017-12-21 20:49 ` Cengiz Can
2017-12-21 20:54 ` Jonathan Corbet [this message]
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=20171221135457.0bd71225@lwn.net \
--to=corbet@lwn.net \
--cc=cengizc@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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 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.