From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Handling of commits in emacs-23 branch and trunk. Date: Wed, 14 Jul 2010 11:27:34 -0400 Message-ID: References: <4C3D6B74.6030500@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1279121274 1078 80.91.229.12 (14 Jul 2010 15:27:54 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 14 Jul 2010 15:27:54 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jan =?iso-8859-1?Q?Dj=E4rv?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 14 17:27:52 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OZ3sA-00041N-LK for ged-emacs-devel@m.gmane.org; Wed, 14 Jul 2010 17:27:46 +0200 Original-Received: from localhost ([127.0.0.1]:36883 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZ3sA-0000Rb-4E for ged-emacs-devel@m.gmane.org; Wed, 14 Jul 2010 11:27:46 -0400 Original-Received: from [199.232.76.173] (port=42703 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZ3s1-0000PZ-1Z for emacs-devel@gnu.org; Wed, 14 Jul 2010 11:27:37 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1OZ3rz-0005X2-WC for emacs-devel@gnu.org; Wed, 14 Jul 2010 11:27:36 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:51371) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1OZ3rz-0005Wy-QE for emacs-devel@gnu.org; Wed, 14 Jul 2010 11:27:35 -0400 Original-Received: from dann by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1OZ3rz-0006Qa-Jj; Wed, 14 Jul 2010 11:27:35 -0400 In-Reply-To: <4C3D6B74.6030500@swipnet.se> ("Jan =?iso-8859-1?Q?Dj=E4rv=22?= =?iso-8859-1?Q?'s?= message of "Wed\, 14 Jul 2010 09\:47\:00 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:127290 Archived-At: Jan Dj=E4rv writes: > Hello. > > Now that trunk ia ANSI-C-ified, how shall emacs-23 commits that change > prototypes or add functions be handeled? Shall we put them in > emacs-23 with P__ + K&R and then fix them in trunk when they get > merged there, or just convert to ANSI-C in emacs-23 also? Add new functions as standard C, there's already a few like that in emacs-23, so it's impossible to compile with a K&R compiler, so using K&R will just generate more work when merging to the trunk. If a function definition/declaration changes, convert it to standard C.