Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Joachim Wiberg <troglobit@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/ssdp-responder: bump to version 1.9
Date: Wed, 2 Nov 2022 22:19:23 +0100	[thread overview]
Message-ID: <20221102211923.GA3918838@scaer> (raw)
In-Reply-To: <20221102180608.4ac368ae@windsurf>

Thomas, All,

On 2022-11-02 18:06 +0100, Thomas Petazzoni via buildroot spake thusly:
> On Tue, 01 Nov 2022 08:18:53 +0100
> Joachim Wiberg <troglobit@gmail.com> wrote:
> > I tried to be as clear as possible about this, even when I did the
> > release upstream.  Maybe I should have been extra clear somehow?
> All we expect is a short note in the commit log, which clarifies that
> the submitter of the patch has changed the hash of the license file
> after properly checking what the changes in the license files are.
> That's really the complete extent of our expectation :-)

I think you missed the part where Joachim *does* priovide that
information  in his commit log, copied below:

    Changes:
     - New command line options to ssdp-scan
     - Update copyright years (affects LICENSE file hash)

So, our expectations were met! ;-)

Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-02 21:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 17:46 [Buildroot] [PATCH 0/3] package/ssdp-responder bump and check-package fixes Joachim Wiberg
2022-10-31 17:46 ` [Buildroot] [PATCH 1/3] package/ssdp-responder: bump to version 1.9 Joachim Wiberg
2022-10-31 20:47   ` Thomas Petazzoni via buildroot
2022-11-01  7:18     ` Joachim Wiberg
2022-11-02 17:06       ` Thomas Petazzoni via buildroot
2022-11-02 21:19         ` Yann E. MORIN [this message]
2022-11-02 21:21           ` Thomas Petazzoni via buildroot
2022-11-02 22:08             ` Joachim Wiberg
2022-11-05 18:45   ` Yann E. MORIN
2022-11-05 18:48     ` Yann E. MORIN
2022-11-06  8:47       ` Joachim Wiberg
2022-10-31 17:46 ` [Buildroot] [PATCH 2/3] package/ssdp-responder: minor update of help text Joachim Wiberg
2022-11-05 18:47   ` Yann E. MORIN
2022-10-31 17:46 ` [Buildroot] [PATCH 3/3] package/ssdp-responder: fix warnings from check-package and shellcheck Joachim Wiberg
2022-10-31 20:49   ` Thomas Petazzoni via buildroot
2022-11-01  7:30     ` Joachim Wiberg
2022-11-05 18:44       ` Yann E. MORIN
2022-11-06  8:54         ` Joachim Wiberg
2022-11-06 18:19         ` [Buildroot] [PATCH v2 1/1] " Joachim Wiberg
2022-11-22 21:39           ` Thomas Petazzoni via buildroot

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=20221102211923.GA3918838@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=troglobit@gmail.com \
    /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