From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; etc/DOC-${version}.buildnumber Date: Sun, 13 Apr 2008 10:07:57 -0400 Message-ID: References: <8763unt4nz.fsf@gmx.de> <87hce7rmbg.fsf@gmx.de> <69379D86-D6D4-4B37-8618-798BFF4F85F6@Freenet.DE> <4627E984-940D-4659-B732-7CB7B160D1C6@Freenet.DE> <94A5168A-F48D-4E1B-A0D9-2CF62BBF7759@Freenet.DE> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1208095694 16070 80.91.229.12 (13 Apr 2008 14:08:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Apr 2008 14:08:14 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, svenjoac@gmx.de To: Peter Dyballa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 13 16:08:45 2008 connect(): Connection refused 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.50) id 1Jl2su-0006NB-DA for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 16:08:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl2sG-0005jO-DJ for ged-emacs-devel@m.gmane.org; Sun, 13 Apr 2008 10:08:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jl2sC-0005j7-4u for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:08:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jl2sA-0005iv-LS for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:07:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jl2sA-0005is-J9 for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:07:58 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jl2sA-0001Bp-FR for emacs-devel@gnu.org; Sun, 13 Apr 2008 10:07:58 -0400 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1Jl2s9-00046p-TG; Sun, 13 Apr 2008 10:07:57 -0400 In-reply-to: <94A5168A-F48D-4E1B-A0D9-2CF62BBF7759@Freenet.DE> (message from Peter Dyballa on Sun, 13 Apr 2008 10:38:08 +0200) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:95103 gmane.emacs.pretest.bugs:22017 Archived-At: > Cc: svenjoac@gmx.de, > emacs-pretest-bug@gnu.org > From: Peter Dyballa > Date: Sun, 13 Apr 2008 10:38:08 +0200 > > Anyway, 'make clean' expresses something like: "make way for > something new." That's not my interpretation of "make clean". It just means "return to the state we had before configure+make". Also, I don't think "make clean" was designed for anything close to the situation where the files are updated en masse from a VCS. Sounds like you want something like "make cvs-clean" or some such.