From: Alejandro Colomar <alx@kernel.org>
To: Simon Barth <simon.barth@gmx.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] slist.3: wfix
Date: Thu, 25 Apr 2024 13:49:01 +0200 [thread overview]
Message-ID: <g4bkaz2d4ukdjdxajlpl2tnshlzbky6tadxdg4pjycmt4g4y5q@hkmk5yd4xas4> (raw)
In-Reply-To: <ZiomDWBQvwzXT7EE@debian>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Thu, Apr 25, 2024 at 11:44:44AM GMT, Alejandro Colomar wrote:
> Hi Simon,
>
> On Thu, Apr 25, 2024 at 12:43:35AM +0200, Simon Barth wrote:
> > On Wed, Apr 24, 2024 at 12:16:23PM +0200, Alejandro Colomar wrote:
> > > Patch applied. Thanks!
> > Thanks a lot! The contribution process was easy and straight forward
> > once I got the mail setup running!
I'm also interested in the mail setup process. I remember it was a bit
difficult for me back then when I sent my first patches to this project,
and had to ask the maintainer of the time, Michael Kerrisk, to point me
to some tutorials that explain it.
What mail client did you use before sending this patch, and was it easy
to find a way to setup your mail for sending to this project? Should I
add links to pages explaining how to set git-send-email(1) up?
I thought of adding a link to <https://git-send-email.io/> in
<CONTRIBUTING.d/mail>.
>
> Nice to hear that! :-)
>
> BTW, now that you mention the contributing process... were the
> CONTRIBUTING.d/* files easy to find and understand?
>
> Have a lovely day!
> Alex
>
> --
> <https://www.alejandro-colomar.es/>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-04-25 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 0:09 [PATCH] slist.3: wfix Simon Barth
2024-04-24 10:16 ` Alejandro Colomar
2024-04-24 22:43 ` Simon Barth
2024-04-25 9:44 ` Alejandro Colomar
2024-04-25 11:49 ` Alejandro Colomar [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=g4bkaz2d4ukdjdxajlpl2tnshlzbky6tadxdg4pjycmt4g4y5q@hkmk5yd4xas4 \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=simon.barth@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).