From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Ignacio Casso <ignaciocasso@hotmail.com>, 53894@debbugs.gnu.org
Subject: bug#53894: 27.2; Clipboard copy -> C-y -> M-y -> Same clipboard copy does not push to kill ring
Date: Tue, 01 Mar 2022 16:19:20 +0100 [thread overview]
Message-ID: <87ee3ln1jb.fsf@gnus.org> (raw)
In-Reply-To: <87sfs233lx.fsf@yahoo.com> (Po Lu's message of "Tue, 01 Mar 2022 08:42:34 +0800")
Po Lu <luangruo@yahoo.com> writes:
> I think that this change will require you to complete some copyright
> paperwork. Could someone tell me if that is indeed the case?
The patch is large, but it's mostly changes to the comments. The actual
code change looks like it's less than 15 lines of significance, so it
shouldn't require a copyright assignment.
But starting that process anyway would be nice, of course, and Ignacio
is doing that, apparently?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-01 15:19 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 9:13 bug#53894: 27.2; Clipboard copy -> C-y -> M-y -> Same clipboard copy does not push to kill ring Ignacio Casso
2022-02-09 11:44 ` Lars Ingebrigtsen
2022-02-09 12:52 ` Ignacio Casso
2022-02-09 20:21 ` Lars Ingebrigtsen
2022-02-10 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 6:20 ` Eli Zaretskii
2022-02-10 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 6:42 ` Lars Ingebrigtsen
2022-02-10 6:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 8:37 ` Lars Ingebrigtsen
2022-02-10 10:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 6:39 ` Lars Ingebrigtsen
2022-02-10 8:06 ` Eli Zaretskii
2022-02-10 8:43 ` Lars Ingebrigtsen
2022-02-10 10:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 11:37 ` Lars Ingebrigtsen
2022-02-10 12:08 ` Eli Zaretskii
2022-02-10 12:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:29 ` Eli Zaretskii
2022-02-10 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:49 ` Lars Ingebrigtsen
2022-02-10 13:20 ` Ignacio Casso
2022-02-11 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 10:24 ` Ignacio Casso
2022-02-11 11:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 11:28 ` Ignacio Casso
2022-02-11 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 12:42 ` Ignacio Casso
2022-02-11 12:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 2:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-27 18:57 ` Ignacio Casso
2022-02-28 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 12:12 ` Ignacio Casso
2022-02-28 13:35 ` Eli Zaretskii
2022-02-28 14:22 ` Ignacio Casso
2022-02-28 13:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 14:35 ` Ignacio Casso
[not found] ` <87wnhfoy5h.fsf@hotmail.com>
2022-02-28 16:10 ` Ignacio Casso
2022-03-01 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 7:51 ` Ignacio Casso
2022-03-01 13:19 ` Eli Zaretskii
2022-03-01 15:29 ` Ignacio Casso
2022-03-02 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-02 7:44 ` Ignacio Casso
2022-03-02 7:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-02 8:37 ` Ignacio Casso
2022-03-02 10:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 7:41 ` Ignacio Casso
2022-03-09 13:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 19:59 ` Ignacio Casso
2022-03-25 6:25 ` Eli Zaretskii
2022-03-29 12:01 ` Ignacio Casso
2022-03-29 13:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 10:15 ` Ignacio Casso
2022-04-01 10:59 ` Eli Zaretskii
2022-04-01 11:23 ` Ignacio Casso
2022-04-01 12:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 12:15 ` Eli Zaretskii
2022-04-01 12:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 12:10 ` Eli Zaretskii
2022-03-01 15:19 ` Lars Ingebrigtsen [this message]
[not found] ` <871qznc4qg.fsf@hotmail.com>
2022-02-28 16:56 ` Ignacio Casso
[not found] ` <87v8xl376s.fsf@hotmail.com>
2022-02-11 12:48 ` Ignacio Casso
[not found] ` <87pmnurelg.fsf@hotmail.com>
2022-02-10 14:29 ` Ignacio Casso
2022-02-11 6:15 ` Lars Ingebrigtsen
2022-02-11 8:16 ` Eli Zaretskii
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=87ee3ln1jb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53894@debbugs.gnu.org \
--cc=ignaciocasso@hotmail.com \
--cc=luangruo@yahoo.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.
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).