unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sven Joachim <svenjoac@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, Peter_Dyballa@Freenet.DE
Subject: Re: 23.0.60; etc/DOC-${version}.buildnumber
Date: Sat, 12 Apr 2008 19:54:11 +0200	[thread overview]
Message-ID: <87hce7rmbg.fsf@gmx.de> (raw)
In-Reply-To: <uiqyn7zqz.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Apr 2008 20:24:20 +0300")

On 2008-04-12 19:24 +0200, Eli Zaretskii wrote:

>> From: Sven Joachim <svenjoac@gmx.de>
>> Cc: Peter Dyballa <Peter_Dyballa@Freenet.DE>,  emacs-pretest-bug@gnu.org
>> Date: Sat, 12 Apr 2008 18:32:32 +0200
>> 
>> On 2008-04-12 15:10 +0200, Eli Zaretskii wrote:
>> 
>> >> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
>> >> Date: Sat, 12 Apr 2008 14:00:23 +0200
>> >> Cc: 
>> >> 
>> >> This file is not deleted by 'make clean', so upon a new build its  
>> >> number is incremented and more and more DOC files get installed.
>> >
>> > I think this is intended, as you still have the Emacs binary from the
>> > previous build (emacs-${version}.buildnumber) around, and could use
>> > it, e.g., for comparison or some other purpose.
>> 
>> That's not true, the Emacs binaries are all deleted by `make clean'.
>
> Maybe I completely misunderstand the issue at hand: are we talking
> about files in the build directory or in the install directory?

The build directory.

> ("make clean" is relevant to the former, not the latter.)

Of course.

> If Peter and you are talking about the build directory, then the
> previous DOC should probably be removed, but do we really want the
> build number NOT to be incremented anyway?

I'm not certain I understand that; make clean removes all the emacs*
binaries from the build tree and therefore should also remove the then
useless DOC-* files.  It probably makes sense to reset the build number
to 1 after that, doesn't it?  Or what do you mean?

Sven




  reply	other threads:[~2008-04-12 17:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 12:00 23.0.60; etc/DOC-${version}.buildnumber Peter Dyballa
2008-04-12 13:10 ` Eli Zaretskii
2008-04-12 15:14   ` Peter Dyballa
2008-04-12 16:43     ` Eli Zaretskii
2008-04-12 19:41       ` Peter Dyballa
2008-04-12 16:32   ` Sven Joachim
2008-04-12 17:24     ` Eli Zaretskii
2008-04-12 17:54       ` Sven Joachim [this message]
2008-04-12 18:57         ` Eli Zaretskii
2008-04-12 19:00           ` Peter Dyballa
2008-04-12 20:30             ` Eli Zaretskii
2008-04-12 20:59               ` Peter Dyballa
2008-04-13  3:18                 ` Eli Zaretskii
2008-04-13  8:38                   ` Peter Dyballa
2008-04-13 14:07                     ` Eli Zaretskii
2008-04-12 20:49           ` Stephen J. Turnbull
2008-04-12 21:04             ` Peter Dyballa
2008-04-12 23:58               ` Stephen J. Turnbull
2008-04-12 19:21         ` Stefan Monnier
2008-04-12 18:55       ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hce7rmbg.fsf@gmx.de \
    --to=svenjoac@gmx.de \
    --cc=Peter_Dyballa@Freenet.DE \
    --cc=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).