qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Sean Wei <me@sean.taipei>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 00/12] Replace FSF postal address with licenses URL
Date: Wed, 25 Jun 2025 18:14:31 +0200	[thread overview]
Message-ID: <adf47487-83fc-4e2f-bfed-1a608fd4263a@redhat.com> (raw)
In-Reply-To: <20250613.qemu.patch@sean.taipei>

On 13/06/2025 18.30, Sean Wei wrote:
> The boiler-plate licence headers in several parts of QEMU still contain
> the obsolete “51 Franklin Street" contact line.
> 
> The Free Software Foundation now recommends using the canonical URL:
> 
>      https://www.gnu.org/licenses/
> 
> 
> This patch updates those headers. The patches are comment-only;
> no source code changes.
> 
> Please review and let me know if any patch should be split, squashed
> or dropped. This is my first patch for the QEMU project, so any
> feedback is greatly appreciated.
> 
> Thanks to Thomas Huth <thuth@redhat.com> for proposing this issue and
> outlining the steps, and to Daniel P. Berrangé <berrange@redhat.com>
> for the clarifications.
> 
> 
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2438

It's rather https://gitlab.com/qemu-project/qemu/-/issues/2974 instead, but 
anyway, thanks for tackling this!

I'll queue the patches (except the one that updates linux-headers) for my 
next pull request.

  Thomas



      parent reply	other threads:[~2025-06-25 16:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 16:30 [PATCH 00/12] Replace FSF postal address with licenses URL Sean Wei
2025-06-13 16:33 ` [PATCH 01/12] COPYING: replace " Sean Wei
2025-06-25 15:41   ` Thomas Huth
2025-06-13 16:38 ` [PATCH 02/12] linux-headers: " Sean Wei
2025-06-25 15:45   ` Thomas Huth
2025-06-13 16:39 ` [PATCH 03/12] libdecnumber: " Sean Wei
2025-06-25 15:51   ` Thomas Huth
2025-06-13 16:43 ` [PATCH 04/12] include/libdecnumber: " Sean Wei
2025-06-25 15:53   ` Thomas Huth
2025-06-13 16:44 ` [PATCH 05/12] include/hw: " Sean Wei
2025-06-14  5:29   ` Cédric Le Goater
2025-06-14 12:58     ` Sean Wei
2025-06-14 15:33       ` Cédric Le Goater
2025-06-14 20:22         ` Sean Wei
2025-06-16  6:31           ` Cédric Le Goater
2025-06-16  7:14         ` Daniel P. Berrangé
2025-06-16  7:13     ` Daniel P. Berrangé
2025-06-16  7:29       ` Cédric Le Goater
2025-06-16  7:47         ` Daniel P. Berrangé
2025-06-16  7:55           ` Cédric Le Goater
2025-06-16 12:49             ` Sean Wei
2025-06-16 13:38               ` Cédric Le Goater
2025-06-16 13:39   ` Cédric Le Goater
2025-06-13 16:46 ` [PATCH 06/12] include/qemu: " Sean Wei
2025-06-25 15:58   ` Thomas Huth
2025-06-13 16:46 ` [PATCH 07/12] util/rcu.c: " Sean Wei
2025-06-25 16:01   ` Thomas Huth
2025-06-13 16:50 ` [PATCH 08/12] hw: " Sean Wei
2025-06-25 16:02   ` Thomas Huth
2025-06-13 16:51 ` [PATCH 09/12] scripts: " Sean Wei
2025-06-25 16:04   ` Thomas Huth
2025-06-13 16:53 ` [PATCH 10/12] contrib: " Sean Wei
2025-06-16  9:18   ` Akihiko Odaki
2025-06-13 16:53 ` [PATCH 11/12] target/xtensa: " Sean Wei
2025-06-13 17:55   ` Max Filippov
2025-06-13 16:54 ` [PATCH 12/12] target/i386/emulate: " Sean Wei
2025-06-16 18:59   ` Wei Liu
2025-06-25 16:14 ` Thomas Huth [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=adf47487-83fc-4e2f-bfed-1a608fd4263a@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=me@sean.taipei \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).