From: 조성빈 <pcr910303@icloud.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jaesup Kwak <veshboo@gmail.com>, emacs-devel@gnu.org
Subject: Re: Contributing other person's work
Date: Mon, 20 May 2019 01:43:09 +0900 [thread overview]
Message-ID: <94B5EFBD-5EFD-4CB9-84C7-0ECF0950293E@icloud.com> (raw)
In-Reply-To: <jwv7eamo11e.fsf-monnier+emacs@gnu.org>
> 2019. 5. 20. 오전 1:39, Stefan Monnier <monnier@iro.umontreal.ca> 작성:
>
>> I would like to contribute a patch to emacs (which adds Emacs xwidget webkit
>> support for macOS Cocoa), but most of it was developed by another person (I
>> just updated the patch periodically as some Emacs internals changed); see
>> https://github.com/veshboo/emacs
>
> Great!
How does the workflow work exactly?̊̈
If I send the patch by email, does one of the core contributors apply the patch onto the current HEAD of remote?
>> He indicated his intention to contribute to mainline (see
>> https://lists.gnu.org/archive/html/emacs-devel/2017-11/msg00662.html and
>> associated messages); and a comment in one of his issues (see
>> https://github.com/veshboo/emacs/issues/5#issuecomment-421777014) indicates
>> that if veshboo(Jaesup Kwak) signed his FSF copyright assignment, others
>> can do the integration for him.
>
> Good.
>
>> Is this true?
>
> Yes, of course.
That’s relieving :-)
>> (If it’s true) Is there a way to check if one has signed the FSF copyright assignment?
>
> He has: it's on file and everything.
As I haven’t signed before, can I ask how to sign the copyright assignment?
>
>
> Stefan
>
>
next prev parent reply other threads:[~2019-05-19 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 15:37 Contributing other person's work 조성빈
2019-05-19 16:39 ` Stefan Monnier
2019-05-19 16:43 ` 조성빈 [this message]
2019-05-19 16:51 ` Stefan Monnier
2019-05-19 17:02 ` 조성빈
2019-05-19 18:48 ` Stefan Monnier
2019-05-19 16:39 ` Paul Eggert
2019-05-19 16:40 ` 조성빈
2019-05-19 16:45 ` Paul Eggert
2019-05-20 18:24 ` Alan Third
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=94B5EFBD-5EFD-4CB9-84C7-0ECF0950293E@icloud.com \
--to=pcr910303@icloud.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=veshboo@gmail.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).