Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Copyright for erofs.5
Date: Thu, 3 Aug 2023 15:23:44 +0200	[thread overview]
Message-ID: <bcd6cfc1-a306-2261-feb6-55936d8cfd05@kernel.org> (raw)
In-Reply-To: <5fa46ghw63mmhbc3go4pvgn2stcetko65lire6gm4exbxklmyu@qituembq5efj>


[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]

On 2023-08-03 13:42, наб wrote:
> On Thu, Aug 03, 2023 at 12:34:44PM +0200, Alejandro Colomar wrote:
>> On 2023-08-03 03:44, наб wrote:
>>> On Thu, Aug 03, 2023 at 02:06:08AM +0200, Alejandro Colomar wrote:
>>>> I'm packaging manpages 6.05.01 for Debian, and while updating the
>>>> d/copyright file, I noticed some glitch.  You attributed erofs.5 to
>>>> mtk.
>>> I copied it from another file (probably tmpfs.5) then edited it,
>>> so I left the header as-is.
>>>
>>>> I guess that was a copy&paste error, isn't it?
>>> Above my pay-grade to categorise this,
>>> or to touch the header on a file I copied.
>> Yeah, but you could have appended yourself.  I bet you wrote something
>> that deserves a copyright, didn't you?  =)
> Never. I'm an avid IP hater and much more so when it means stuffing
> brands into headers. I'd release it into the public domain if I could.

Ok.

> 
> Best,

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-08-03 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  0:06 Copyright for erofs.5 Alejandro Colomar
2023-08-03  1:44 ` наб
2023-08-03 10:34   ` Alejandro Colomar
2023-08-03 11:42     ` наб
2023-08-03 13:23       ` 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=bcd6cfc1-a306-2261-feb6-55936d8cfd05@kernel.org \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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