From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Michal Nazarewicz" Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] lisp/server.el: Introduction of server-auth-key variable Date: Fri, 29 Apr 2011 14:43:12 +0200 Message-ID: References: <835b9d42b15c18e5adf7381138f347061fbc17e8.1298381336.git.mina86@mina86.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1304108083 3446 80.91.229.12 (29 Apr 2011 20:14:43 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 29 Apr 2011 20:14:43 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 29 22:14:39 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QFu5H-0005A1-Ei for ged-emacs-devel@m.gmane.org; Fri, 29 Apr 2011 22:14:39 +0200 Original-Received: from localhost ([::1]:32881 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QFu5G-0005RZ-Qq for ged-emacs-devel@m.gmane.org; Fri, 29 Apr 2011 16:14:38 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:49822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QFn2S-00022Q-2k for emacs-devel@gnu.org; Fri, 29 Apr 2011 08:43:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QFn2R-0005ga-9e for emacs-devel@gnu.org; Fri, 29 Apr 2011 08:43:16 -0400 Original-Received: from mail-fx0-f41.google.com ([209.85.161.41]:43243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QFn2R-0005gU-3t for emacs-devel@gnu.org; Fri, 29 Apr 2011 08:43:15 -0400 Original-Received: by fxm18 with SMTP id 18so3129452fxm.0 for ; Fri, 29 Apr 2011 05:43:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:to:cc:subject:references :date:mime-version:content-transfer-encoding:from:message-id :in-reply-to:user-agent; bh=rZ+XWP5O4DvGLmA2GEKq+FzncCouXfmvva+tFN3R6+A=; b=p1mZMNbd6WpvIy8z4w4/wSiIaiUwTTb5L/GABtpA1T/b7myoW83SW8QI10p5V5FPnL DqRBGzvDOCeezP5zerHR5bmfAuzWwFitr+Z23Jl3hOCNHT7+7/DANyZk+AFnn5MdVwrH v5eYLot0iCeKUBwlyAGa3jFppAVh+dWGgkU9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; b=eEr4fkG63PAWVHQ/zU62YVz5hqNE3le75PYKZiZS4tLVhAd7cJAjt8I3OKzGtY7o2l 6uc7HQOPsFaWcO4LfOOJ7mliRgMN2gQNl7sWs12kKY5+GKg03YakCWqkHgycXkyvyI0Q Kz3plOwqduIyrAQgzld1kI4JuJaWIsmc4H8m8= Original-Received: by 10.223.69.65 with SMTP id y1mr3128052fai.60.1304080994188; Fri, 29 Apr 2011 05:43:14 -0700 (PDT) Original-Received: from mnazarewicz-glaptop (dhcp-172-16-75-204.zrh.corp.google.com [172.16.75.204]) by mx.google.com with ESMTPS id l3sm889319fap.12.2011.04.29.05.43.13 (version=SSLv3 cipher=OTHER); Fri, 29 Apr 2011 05:43:13 -0700 (PDT) In-Reply-To: User-Agent: Opera Mail/11.10 (Linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.161.41 X-Mailman-Approved-At: Fri, 29 Apr 2011 16:14:35 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:138911 Archived-At: > 2011/4/29 Michal Nazarewicz wrote: >> The patch seemed rather straightforward but if you guys decide to >> include it and papers need to be signed just let me know as it >> should not be a problem. On Fri, 29 Apr 2011 14:02:10 +0200, Juanma Barranquero wrote: > As soon as the contributions amount to more than 10-15 lines of > non-trivial code, papers must be signed. The patch was just a bit of documentation, a piece of code moved to a separate function and a single (or ...) added hence I considered it trivial. At any rate, copyright assignment should not be a problem, but since Google holds the copyright for the patch I need to contact legal. Could you just point me to the forms? -- Best regards, _ _ .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal "mina86" Nazarewicz (o o) ooo +----------ooO--(_)--Ooo--