all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r103740: Remove some files	that autoreconf can supply.
Date: Fri, 25 Mar 2011 19:54:39 +0200	[thread overview]
Message-ID: <837hbnt7a8.fsf@gnu.org> (raw)
In-Reply-To: <xz1v1vazti.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 25 Mar 2011 13:13:13 -0400
> Cc: emacs-devel@gnu.org
> 
> I understand this point, but these are "generated" (sort of...) files.
> The history is not important. Indeed, the history has been reset, since
> they are now the versions that automake-1.11 supplies rather than the
> versions that were previously in Emacs. In some sense, they aren't even
> the same files. The "missing" that you use to build Emacs isn't in the
> repo any more. Instead there is a fallback that you can copy into place
> if you really need to. That is why I did not "move" them.

I think at least the history of src/config.in and lib/Makefile.in
should be preserved, since they are affiliated with Emacs (unlike the
other files which are brought from outside).  Does anyone object to
restoring the history of these two files?



  parent reply	other threads:[~2011-03-25 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Q31HA-0000Ss-8f@colonialone.fsf.org>
2011-03-25 16:27 ` [Emacs-diffs] /srv/bzr/emacs/trunk r103740: Remove some files that autoreconf can supply Stefan Monnier
2011-03-25 17:13   ` Glenn Morris
2011-03-25 17:27     ` Óscar Fuentes
2011-03-25 17:54     ` Eli Zaretskii [this message]
2011-03-25 18:13       ` Glenn Morris
2011-03-25 19:38         ` Eli Zaretskii
2011-03-25 19:48           ` Glenn Morris
2011-03-25 21:21     ` Stefan Monnier
2011-03-26 19:33       ` Tom Tromey

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=837hbnt7a8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@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 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.