From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?B?7KGw7ISx67mI?= Newsgroups: gmane.emacs.devel Subject: Re: Contributing other person's work Date: Mon, 20 May 2019 02:02:07 +0900 Message-ID: <121DA8FE-20B7-490E-B000-05AB9361C7C7@icloud.com> References: <77FDCED5-5206-4221-90A4-5797A0937CC7@icloud.com> <94B5EFBD-5EFD-4CB9-84C7-0ECF0950293E@icloud.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) 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="128794"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Jaesup Kwak , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 19 19:03:05 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 1hSPDE-000XNJ-NM for ged-emacs-devel@m.gmane.org; Sun, 19 May 2019 19:03:04 +0200 Original-Received: from localhost ([127.0.0.1]:51126 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSPDD-00045Q-M8 for ged-emacs-devel@m.gmane.org; Sun, 19 May 2019 13:03:03 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:51135) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSPCP-00045I-9s for emacs-devel@gnu.org; Sun, 19 May 2019 13:02:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hSPCO-0001nI-8V for emacs-devel@gnu.org; Sun, 19 May 2019 13:02:13 -0400 Original-Received: from pv50p00im-ztdg10011301.me.com ([17.58.6.40]:59697) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hSPCN-0001mg-Vi for emacs-devel@gnu.org; Sun, 19 May 2019 13:02:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1558285330; bh=T5ZCD/JwhYynCAcGOuA1T9f61WfMVM82sokIPZVH9gY=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=pPl6wBujL9WtYQ1pJW0mX4hBmJ0yF6982QZfyuBdp34AxF7J8YD1/Q6mWYxwwsqXn OoYNflTFHKMTkaE8rwCF6CcInEPreO1Aa1iQhwcy4/Wjb2QjoY5Zhc/jsRcfxBOdhP cZhNPNxKszdNuZMb8TBYqZ8cttfKOnnpjViTZG7hwbYL0n19Vqv27nNeOrcn7tTYlX WAig1TcI/4yj4W9NTVw9hQFEwlKI36yiWYVf4fbcFniE05icD0Fsq9olR754lJo//Y O3d7bdw4b1Ph6nqnfy7NfkX/zeW3x5anzIs43y3XIPW3KdhlBIDqyQtmW19DoZRiH2 cFWmq1KlAKqeQ== Original-Received: from [192.168.0.11] (unknown [1.230.108.64]) by pv50p00im-ztdg10011301.me.com (Postfix) with ESMTPSA id 913A9640773; Sun, 19 May 2019 17:02:09 +0000 (UTC) In-Reply-To: X-Mailer: Apple Mail (2.3445.9.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-19_11:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=998 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1905190124 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 17.58.6.40 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:236756 Archived-At: > 2019. 5. 20. =EC=98=A4=EC=A0=84 1:51, Stefan Monnier = =EC=9E=91=EC=84=B1: >=20 >> 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? >=20 > 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. I would like the patch workflow better as I was maintaining the patch = only :-) >>> He has: it's on file and everything. >> As I haven=E2=80=99t signed before, can I ask how to sign the = copyright assignment? >=20 > Sure: fill the form below and email it as instructed to the FSF so = they > can send you the relevant paperwork to sign, Before I have to wait two weeks to get my paperwork (and it=E2=80=99s = hard to get my paperwork as mail here for special reasons...), I think(maybe not) I heard a news a year or two ago that FSF started to = allowing digital signing with gpg=E2=80=A6 Is that true? If it is, I would prefer the digital-way=E2=80=A6 >=20 > Stefan >=20 >=20 > Please email the following information to assign@gnu.org, and we > will send you the assignment form for your past and future changes. >=20 > Please use your full legal name (in ASCII characters) as the subject > line of the message. > ---------------------------------------------------------------------- > REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES >=20 > [What is the name of the program or package you're contributing to?] > Emacs >=20 > [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.] >=20 >=20 > [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?] >=20 >=20 > [For the copyright registration, what country are you a citizen of?] >=20 >=20 > [What year were you born?] >=20 >=20 > [Please write your email address here.] >=20 >=20 > [Please write your postal address here.] >=20 >=20 >=20 >=20 >=20 > [Which files have you changed so far, and which new files have you = written > so far?] >=20