all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, Peter_Dyballa@Freenet.DE,
	Sven Joachim <svenjoac@gmx.de>
Subject: Re: 23.0.60; etc/DOC-${version}.buildnumber
Date: Sun, 13 Apr 2008 05:49:18 +0900	[thread overview]
Message-ID: <87d4ouiysx.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <uhce699zh.fsf@gnu.org>

Eli Zaretskii writes:

 > I meant that perhaps the build number should grow even after "make
 > clean".

Yes, it should, unless "make clean" reverts all the source changes
that might affect DOC.  That "cleaned" build might very well have been
installed to preserve it for later comparisons.  Then it is very
useful to have a convenient unique identifier for each build.




  parent reply	other threads:[~2008-04-12 20:49 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=87d4ouiysx.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=Peter_Dyballa@Freenet.DE \
    --cc=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=svenjoac@gmx.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.