From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Please help get ready for proofreading of Emacs manual Date: Thu, 21 Sep 2017 10:59:39 +0300 Message-ID: <83377gfpn8.fsf@gnu.org> References: <87fubjepj7.fsf@jane> <87377i10dr.fsf@jane> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1505980835 15511 195.159.176.226 (21 Sep 2017 08:00:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 21 Sep 2017 08:00:35 +0000 (UTC) Cc: charles@aurox.ch, rms@gnu.org, emacs-devel@gnu.org To: John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 21 10:00:30 2017 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 1duwPJ-0003R0-3I for ged-emacs-devel@m.gmane.org; Thu, 21 Sep 2017 10:00:25 +0200 Original-Received: from localhost ([::1]:52249 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duwPO-0001uK-Ri for ged-emacs-devel@m.gmane.org; Thu, 21 Sep 2017 04:00:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36378) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duwOr-0001u5-0c for emacs-devel@gnu.org; Thu, 21 Sep 2017 03:59:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1duwOn-0003uC-4s for emacs-devel@gnu.org; Thu, 21 Sep 2017 03:59:57 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58172) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duwOn-0003u7-0K; Thu, 21 Sep 2017 03:59:53 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4202 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1duwOf-0003EN-QE; Thu, 21 Sep 2017 03:59:46 -0400 In-reply-to: (message from John Wiegley on Wed, 20 Sep 2017 15:03:43 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:218623 Archived-At: > From: John Wiegley > Date: Wed, 20 Sep 2017 15:03:43 -0700 > Cc: charles@aurox.ch, emacs-devel@gnu.org > > >>>>> "RS" == Richard Stallman writes: > > >> How about a commit on some specialized branch? > RS> It is for the Emacs maintainers to decide whether that method is ok. They > RS> are the ones who will need to use it. > > I think having a branch devoted to manual edits is a good idea, something > branched off of emacs-26 that we can frequently merge back. Please don't. Each additional branch brings some overhead to work with it, and also a non-negligible probability of making mistakes, like pushing to the wrong branch. Separate branches are justified for experimental code changes, because they avoid breaking the main branches which many people follow. But documentation can never break anything, and any non-trivial changes in it need to be reviewed anyway. So I see no need for a branch, it would just be an unnecessary nuisance and source of errors. Proposed changes for the manuals should be posted in the usual manner: with "M-x report-emacs-bug RET". TIA