From: goranmoomin@daum.net
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58271@debbugs.gnu.org, Po Lu <luangruo@yahoo.com>
Subject: bug#58271: 29.0.50; [PATCH] Handle sharing Cocoa xwidgets more gracefully
Date: Tue, 4 Oct 2022 08:01:25 +0900 [thread overview]
Message-ID: <276AB2FF-9AD1-48C4-BD87-FD2890E82762@daum.net> (raw)
In-Reply-To: <87czb86b4g.fsf@gnus.org>
2022. 10. 4. 오전 3:00, Lars Ingebrigtsen <larsi@gnus.org> 작성:
>
> 조성빈 <goranmoomin@daum.net> writes:
>
>> The attached patch fixes this issue by showing a warning label in the place of
>> the xwidget view.
>
> Makes sense to me -- perhaps Po Lu has some comments; added to the CCs.
>
> In any case, it looks like this patch is too large to apply without
> getting a copyright assignment for the FSF first. Would you be willing
> to sign such paper?
I’ve signed the paper, though I’ve used a different email address before. (I’m
Sungbin Jo <pcr910303 <at> icloud.com> who contributed the original Cocoa
xwidget patch in bug#29565.)
Would changing my email address require going through the process again?
Thanks.
next prev parent reply other threads:[~2022-10-03 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 9:32 bug#58271: 29.0.50; [PATCH] Handle sharing Cocoa xwidgets more gracefully 조성빈
2022-10-03 18:00 ` Lars Ingebrigtsen
2022-10-03 23:01 ` goranmoomin [this message]
2022-10-03 23:35 ` Lars Ingebrigtsen
2022-10-04 0:01 ` Sungbin Jo
2022-10-04 4:42 ` Stefan Kangas
2022-10-04 6:48 ` Eli Zaretskii
2022-10-04 7:25 ` Sungbin Jo
2022-11-11 13:27 ` Stefan Kangas
2022-10-04 0:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 2:03 ` Sungbin Jo
2022-11-25 1:26 ` Stefan Kangas
2022-11-25 2:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 5:31 ` 조성빈
2022-11-26 5:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=276AB2FF-9AD1-48C4-BD87-FD2890E82762@daum.net \
--to=goranmoomin@daum.net \
--cc=58271@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.