unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
To: rgm@gnu.org
Cc: 13965@debbugs.gnu.org, bug-texinfo@gnu.org
Subject: bug#13965: info.info conflict between emacs and texinfo
Date: Tue, 2 Apr 2013 21:25:14 GMT	[thread overview]
Message-ID: <201304022125.r32LPEU4015513__8973.15135594017$1364937995$gmane$org@freefriends.org> (raw)
In-Reply-To: <qkmwtgrjwb.fsf@fencepost.gnu.org>

    If it really helps you, we could rename it. 

Well, obviously it is not a stopper.  I can edit the file when I import
it and ignore that difference.

    We'll have to change 58 files, several of which also live in other
    repositories.

The point is that nearly every other package in GNU uses fdl.texi (as
far as I have seen).  Why should Emacs use a different name for the
file?  It just seems wrong.

    It won't make any difference to this issue (I assume), 

Indeed.

k





  parent reply	other threads:[~2013-04-02 21:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 11:01 info.info conflict between emacs and texinfo Andreas Schwab
2013-03-18 19:00 ` Karl Berry
2013-03-30  1:02   ` bug#13965: " Glenn Morris
2013-03-30  1:07     ` Glenn Morris
2013-03-30  5:36       ` Eli Zaretskii
2013-03-31 23:21     ` Karl Berry
     [not found] ` <201303312321.r2VNLkox020803@freefriends.org>
2013-04-01  7:11   ` Andreas Schwab
     [not found] ` <m2a9pi67yj.fsf@linux-m68k.org>
2013-04-01 22:34   ` Karl Berry
2013-04-02  7:43   ` Petr Hracek
2013-04-02 16:16     ` Glenn Morris
2013-04-03 11:13       ` Petr Hracek
     [not found] ` <qkmwtgrjwb.fsf@fencepost.gnu.org>
2013-04-02 21:25   ` Karl Berry [this message]
     [not found] <201304012234.r31MYN0N023983@freefriends.org>
2013-04-02 16:12 ` Glenn Morris
     [not found] <201304022125.r32LPEU4015513@freefriends.org>
2013-04-03  0:24 ` Glenn Morris
     [not found] <20130318230008.GD31358@gamma.logic.tuwien.ac.at>
     [not found] ` <86d2uwl2mu.fsf@frenzy.freefriends.org>
     [not found]   ` <8761276fgh.fsf@igel.home>
2015-10-17 19:55     ` Gavin Smith
     [not found]     ` <CAKPWYQ2m5T1Mx0q6usVY47OMsXRYt3rHcU8TU9WvWDwdXzTpjw@mail.gmail.com>
2015-10-17 21:38       ` Glenn Morris
     [not found]       ` <rqd1wddvkj.fsf@fencepost.gnu.org>
2015-10-17 22:28         ` Gavin Smith
     [not found]         ` <CAKPWYQ0BveDKDKoqXECurEJqbs+VKtJu5XdrUq95mjv=311idg@mail.gmail.com>
2015-10-18 18:05           ` Glenn Morris
     [not found]           ` <0q1tcs3vdi.fsf@fencepost.gnu.org>
2015-10-18 19:28             ` Andreas Schwab
2015-10-18 19:31             ` Glenn Morris
     [not found]             ` <874mho7z7t.fsf@igel.home>
2015-10-18 19:34               ` Glenn Morris
2015-10-18 19:41             ` Gavin Smith
     [not found]             ` <ota8rg2ctk.fsf@fencepost.gnu.org>
2015-10-18 19:44               ` Glenn Morris

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='201304022125.r32LPEU4015513__8973.15135594017$1364937995$gmane$org@freefriends.org' \
    --to=karl@freefriends.org \
    --cc=13965@debbugs.gnu.org \
    --cc=bug-texinfo@gnu.org \
    --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 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).