unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: emacs-pretest-bug@gnu.org, svenjoac@gmx.de
Subject: Re: 23.0.60; etc/DOC-${version}.buildnumber
Date: Sun, 13 Apr 2008 10:07:57 -0400	[thread overview]
Message-ID: <E1Jl2s9-00046p-TG@fencepost.gnu.org> (raw)
In-Reply-To: <94A5168A-F48D-4E1B-A0D9-2CF62BBF7759@Freenet.DE> (message from Peter Dyballa on Sun, 13 Apr 2008 10:38:08 +0200)

> Cc: svenjoac@gmx.de,
>  emacs-pretest-bug@gnu.org
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> 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.




  reply	other threads:[~2008-04-13 14:07 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 [this message]
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=E1Jl2s9-00046p-TG@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=Peter_Dyballa@Freenet.DE \
    --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 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).