From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Contributing other person's work Date: Sun, 19 May 2019 12:51:20 -0400 Message-ID: References: <77FDCED5-5206-4221-90A4-5797A0937CC7@icloud.com> <94B5EFBD-5EFD-4CB9-84C7-0ECF0950293E@icloud.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="75312"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Jaesup Kwak , emacs-devel@gnu.org To: =?utf-8?B?7KGw7ISx67mI?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 19 18:51:32 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSP23-000JUT-Va for ged-emacs-devel@m.gmane.org; Sun, 19 May 2019 18:51:32 +0200 Original-Received: from localhost ([127.0.0.1]:51044 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSP22-0001PU-Ty for ged-emacs-devel@m.gmane.org; Sun, 19 May 2019 12:51:30 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:49718) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSP1w-0001PP-Vo for emacs-devel@gnu.org; Sun, 19 May 2019 12:51:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hSP1v-0004lC-W5 for emacs-devel@gnu.org; Sun, 19 May 2019 12:51:24 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:42771) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hSP1v-0004iA-Ox for emacs-devel@gnu.org; Sun, 19 May 2019 12:51:23 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id B955A1011B6; Sun, 19 May 2019 12:51:22 -0400 (EDT) Original-Received: from mail02.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 7BAFB1007CC; Sun, 19 May 2019 12:51:21 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1558284681; bh=jvAla+Iq8st6Vt4A7aKvcdyKJZvBDBRxHggpYbH4lno=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=daOQDk4CN84qER3inNgSN5MyTZ3MximIFEjm51jcz6P7WEleZ3DW0eQ3QrzuK2LeI m66yTAlPWCopQkpW3aDAeCqv3K29G4VzSITwZ/uy3xQIg0NPyxZYd8NN0Ptfd8jaC+ A6GtpX8EZ2X7ewmK8x0PuZfIKdhAe8KJ5c1uLnLOxF+22kC3QTfN9c56UbU4xwJQcD HmLfPKhtjgmPaKiyCUW0EnCy+1e0ZDHpZRlDHT4DivcQnV2J19VS5FQKvgwnwH8cSL Wu0LSf6KYOYCf4/8AVf/WdGoONiVF27nUQa8Fs9Voe2t9coFmS6l5ZgUPNwajyNqwk HXFV/eHhRROUg== Original-Received: from ceviche (unknown [216.154.3.168]) by mail02.iro.umontreal.ca (Postfix) with ESMTPSA id 34187120B82; Sun, 19 May 2019 12:51:21 -0400 (EDT) In-Reply-To: <94B5EFBD-5EFD-4CB9-84C7-0ECF0950293E@icloud.com> (=?utf-8?B?IuyhsOyEseu5iCIncw==?= message of "Mon, 20 May 2019 01:43:09 +0900") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236755 Archived-At: > How does the workflow work exactly?=CC=8A=CC=88 > If I send the patch by email, does one of the core contributors apply the > patch onto the current HEAD of remote? Yes, that's one way. Another is to point to a Git branch. I'm not sure whether we want the faithful commit history in this case: I usually like it, but if there's been too many "merge from master" that end up drowning the real commits, it might be worth the trouble of reworking the history a bit (e.g. going back to the last real commit merge that into master). Also, the commit messages may require improvements, which would again require rewriting the history. >> He has: it's on file and everything. > As I haven=E2=80=99t signed before, can I ask how to sign the copyright a= ssignment? Sure: fill the form below and email it as instructed to the FSF so they can send you the relevant paperwork to sign, Stefan Please email the following information to assign@gnu.org, and we will send you the assignment form for your past and future changes. Please use your full legal name (in ASCII characters) as the subject line of the message. ---------------------------------------------------------------------- REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES [What is the name of the program or package you're contributing to?] Emacs [Did you copy any files or text written by someone else in these changes? Even if that material is free software, we need to know about it.] [Do you have an employer who might have a basis to claim to own your changes? Do you attend a school which might make such a claim?] [For the copyright registration, what country are you a citizen of?] [What year were you born?] [Please write your email address here.] [Please write your postal address here.] [Which files have you changed so far, and which new files have you written so far?]