From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] netcat-openbsd: add source and license hashes
Date: Thu, 23 Nov 2017 22:48:33 +0100 [thread overview]
Message-ID: <20171123224833.562c69d3@windsurf.lan> (raw)
In-Reply-To: <20171123210734.z2n7xeretrwy2tdu@archlinux>
Hello,
On Thu, 23 Nov 2017 16:07:34 -0500, Ga?l PORTAY wrote:
> On Thu, Nov 23, 2017 at 09:32:42PM +0100, Thomas Petazzoni wrote:
> > Hello,
> >
> > On Sat, 18 Nov 2017 20:54:58 -0500, Ga?l PORTAY wrote:
> > > Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> > > ---
> > > Hi,
> >
> > Applied to next, thanks.
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Free Electrons
> > Embedded Linux, Kernel and Android engineering
> > http://free-electrons.com
>
> Thanks,
Thanks a lot for your "thanks", but it's not really needed to thank
back the maintainers when they merge a patch. We already have three
e-mails per patches on the list:
- One with the patch itself
- One sent by Git when the commit is merged/pushed
- One sent by the maintainer to notify the author that the patch was
merged.
I don't think it's really useful to add a fourth patch with the
contributor thanking the maintainer.
Just pay a beer to one of the maintainers the next time you see him :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-23 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 1:54 [Buildroot] [PATCH] netcat-openbsd: add source and license hashes Gaël PORTAY
2017-11-23 20:32 ` Thomas Petazzoni
2017-11-23 21:07 ` Gaël PORTAY
2017-11-23 21:48 ` Thomas Petazzoni [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=20171123224833.562c69d3@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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