unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: No rule to make target `../lib/ignore-value.h'
Date: Tue, 09 Jul 2013 14:03:08 -0400	[thread overview]
Message-ID: <9qwqozpq5f.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83txk3vcvn.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Jul 2013 20:53:16 +0300")

Eli Zaretskii wrote:

>> > How do you discourage volunteers from scratching their itches?
>> 
>> Well, removing those files would surely do it.
>
> It's as easy to restore a removed file as it is to remove it.  One can
> even do that and keep the original file ID, so the history is intact.

I was being flippant.
Obviously, we can discourage things by stating that they are discouraged.
No, we cannot stop people forking Emacs and doing whatever they want
with the build system, but "we" can make policy decisions and say "no
thanks, we do not want that code in Emacs".



  reply	other threads:[~2013-07-09 18:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  9:08 No rule to make target `../lib/ignore-value.h' martin rudalics
2013-07-09  9:55 ` Juanma Barranquero
2013-07-09 10:35   ` martin rudalics
2013-07-09 11:36     ` Juanma Barranquero
2013-07-09 13:07       ` martin rudalics
2013-07-09 13:48         ` Juanma Barranquero
2013-07-09 16:18         ` Eli Zaretskii
2013-07-09 14:48       ` Paul Eggert
2013-07-09 14:55         ` Juanma Barranquero
2013-07-09 16:05           ` Glenn Morris
2013-07-09 16:07             ` Juanma Barranquero
2013-07-09 16:11               ` Glenn Morris
2013-07-09 16:22                 ` Juanma Barranquero
2013-07-10  9:18                 ` martin rudalics
2013-07-10  9:43                   ` Andreas Schwab
2013-07-10  9:53                     ` martin rudalics
2013-07-10 10:25                   ` Juanma Barranquero
2013-07-10 12:16                     ` martin rudalics
2013-07-10 14:13                       ` Juanma Barranquero
2013-07-10 15:50                       ` Eli Zaretskii
2013-07-09 17:12             ` Eli Zaretskii
2013-07-09 17:21               ` Glenn Morris
2013-07-09 17:53                 ` Eli Zaretskii
2013-07-09 18:03                   ` Glenn Morris [this message]
2013-07-09 18:11                     ` Eli Zaretskii
2013-07-09 18:15                       ` Glenn Morris
2013-07-09 18:24                         ` Eli Zaretskii
2013-07-09 16:23         ` Eli Zaretskii
2013-07-09 16:14       ` Eli Zaretskii
2013-07-09 16:17         ` Juanma Barranquero
2013-07-09 17:13           ` Eli Zaretskii
2013-07-09 17:28             ` Juanma Barranquero
2013-07-09 16:16       ` Eli Zaretskii
2013-07-09 16:20         ` Juanma Barranquero
2013-07-09 17:14           ` Eli Zaretskii

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=9qwqozpq5f.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).