From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Checking in files with trailing white space Date: Tue, 13 Dec 2016 14:39:23 -0800 Organization: UCLA Computer Science Department Message-ID: <053170b4-0258-bf23-c20b-236be50c984b@cs.ucla.edu> References: <20161211133110.GB14084@acm.fritz.box> <20161212221642.GA4361@acm.fritz.box> <83wpf4bj26.fsf@gnu.org> <366009d8-72f4-2f85-103c-214a5e111e77@cs.ucla.edu> <83oa0fbyx6.fsf@gnu.org> <8360mnbqnz.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1481668924 9137 195.159.176.226 (13 Dec 2016 22:42:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 13 Dec 2016 22:42:04 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 13 23:42:00 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cGvlm-0001Qq-Ju for ged-emacs-devel@m.gmane.org; Tue, 13 Dec 2016 23:41:58 +0100 Original-Received: from localhost ([::1]:58479 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGvlq-0006NI-FC for ged-emacs-devel@m.gmane.org; Tue, 13 Dec 2016 17:42:02 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGvjO-0004Me-O3 for emacs-devel@gnu.org; Tue, 13 Dec 2016 17:39:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGvjN-00030G-Ub for emacs-devel@gnu.org; Tue, 13 Dec 2016 17:39:30 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:58190) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cGvjK-0002yy-6r; Tue, 13 Dec 2016 17:39:26 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id CAFD516009D; Tue, 13 Dec 2016 14:39:24 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id TcWpSIV_kQeP; Tue, 13 Dec 2016 14:39:24 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 1193016009E; Tue, 13 Dec 2016 14:39:24 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 1zpHqmLfoOX2; Tue, 13 Dec 2016 14:39:23 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id E872C16009D; Tue, 13 Dec 2016 14:39:23 -0800 (PST) In-Reply-To: <8360mnbqnz.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:210417 Archived-At: On 12/13/2016 11:00 AM, Eli Zaretskii wrote: > Producing arbitrary output from a text description might not be easy. It might not be; but ordinarily it is, for the test data that Emacs needs. > I'm not sure this is relevant here. E.g., we distribute Emacs sources > as a compressed archive, not as a set of plain-text files. That is merely an issue of efficient data transfer. We use a convenient format (compressed tarball) that is universally understood to stand for a set of source files, and it's OK to do that. It would become not-OK if we had a complicated or error-prone procedure for deriving the source code, or expected people to reverse-engineer object code within the tarball. It's common practice for closed-source software developers to do that sort of thing. For example, they may purposely obscure the source code, and ship object files (in the GPL sense) that they call "source files" (because you can feed them to a compiler). Although we are obviously not doing that here, we should avoid even a whiff of doing so, so as to set a good example.