From: nipponpost@airmail.cc
To: Juanma Barranquero <lekktu@gmail.com>
Cc: bug-gnu-emacs
<bug-gnu-emacs-bounces+nipponpost=airmail.cc@gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>,
Richard Stallman <rms@gnu.org>,
38002@debbugs.gnu.org
Subject: bug#38002: Please remove this joke
Date: Sat, 02 Nov 2019 15:57:46 +0000 [thread overview]
Message-ID: <78176dc42c04668c2e8a9b4386f7c76d@airmail.cc> (raw)
In-Reply-To: <CAAeL0SRqj4Q6R37qgOQKScVUDPDmedVq3fM-eQV5+auh6JtdLg@mail.gmail.com>
I am going to find who actually created the joke, if at all I possibly
can, and inform HIM about copyright reversion under section 203 of the
Copyright Act.
Additionally, in the fullness of time, I will also inform your Estate
about said feature of the Copyright Act, along with all others who
contributed code to free-software I can find who are affected by this
war against sexism.
I will inform the Estates and Persons of the damages they can claim if
the notice of reversion is not complied with, I will also inform them
about derivative works and how any replacement code my very-well be
derivative.
On 2019-11-02 02:14, Juanma Barranquero wrote:
> On Sat, Nov 2, 2019 at 12:44 AM <nipponpost@airmail.cc> wrote:
>
>> And I am going to find out who added that joke, if at all I possibly
>> can, and inform him about copyright reversion under section 203 of
> the
>> Copyright Act.
>
> I compiled the original jokes, and committed the file.
>
> And I'm glad the joke has been removed. It was sexist. I wasn't aware
> then, but I am now.
next prev parent reply other threads:[~2019-11-02 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:29 bug#38002: Please remove this joke Cecilio Pardo
2019-10-31 15:46 ` Stefan Kangas
2019-10-31 16:22 ` Marcin Borkowski
2019-10-31 20:24 ` Robert Pluim
2019-10-31 16:25 ` Lars Ingebrigtsen
2019-10-31 19:24 ` Glenn Morris
2019-10-31 23:12 ` Juanma Barranquero
2019-11-01 0:40 ` nipponpost
2019-11-01 13:15 ` Filipp Gunbin
2019-11-01 14:29 ` Richard Stallman
2019-11-01 15:24 ` nipponpost
2019-11-01 16:23 ` Marcin Borkowski
2019-11-01 20:13 ` cpardo
2019-11-01 23:13 ` nipponpost
2019-11-02 8:46 ` Marcin Borkowski
[not found] ` <237201ce8334abb8f7dfb4612ed9db08@airmail.cc>
2019-11-03 13:21 ` Richard Stallman
2019-11-01 20:30 ` nipponpost
2019-11-02 8:52 ` Marcin Borkowski
2019-11-01 16:21 ` Lars Ingebrigtsen
2019-11-01 23:25 ` nipponpost
2019-11-02 2:14 ` Juanma Barranquero
2019-11-02 15:57 ` nipponpost [this message]
2019-11-01 2:22 ` Richard Stallman
2019-11-01 12:55 ` Lars Ingebrigtsen
[not found] ` <mailman.425.1572711186.13325.bug-gnu-emacs@gnu.org>
2019-11-02 21:06 ` Alan Mackenzie
2019-11-03 16:45 ` bug#38002: Please remove this joke - Informing of legal rights is not a threat - 35 year copyright recovery for non-works-for-hire nipponpost
2019-11-03 17:01 ` bug#38002: Please remove this joke Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78176dc42c04668c2e8a9b4386f7c76d@airmail.cc \
--to=nipponpost@airmail.cc \
--cc=38002@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+nipponpost=airmail.cc@gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.com \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).