unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,  emacs-devel@gnu.org,  v.pupillo@gmail.com
Subject: Re: master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569).
Date: Wed, 06 Mar 2024 11:20:08 -0500	[thread overview]
Message-ID: <yp1sf13uybr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp14jdjwnai.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Wed, 06 Mar 2024 07:35:33 -0500")

Andrea Corallo <acorallo@gnu.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Po Lu <luangruo@yahoo.com>
>>> Cc: Vincenzo Pupillo <v.pupillo@gmail.com>
>>> Date: Wed, 06 Mar 2024 09:35:59 +0800
>>> 
>>> Andrea Corallo <acorallo@gnu.org> writes:
>>> 
>>> > -	      cp type_hierarchy* $(DESTDIR)${infodir}/; \ # Used by elisp.info.
>>> > +	      cp type_hierarchy* $(DESTDIR)${infodir}/; \
>>> >  	   done; \
>>> >  	fi
>>> >  
>>> 
>>> Wouldn't it be proper to attach a unique prefix to the names of these
>>> files, in case Emacs is not the only program interested in distributing
>>> a "type_hierarchy.jpg" with its manuals?
>>
>> Indeed, I think something like elisp_type_hierarchy.jpg should be a
>> better name.
>
> SGTM will do.

Should be done.

  Andrea



      reply	other threads:[~2024-03-06 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170967469435.3222.6723689814001594119@vcs2.savannah.gnu.org>
     [not found] ` <20240305213814.AABFFC00231@vcs2.savannah.gnu.org>
2024-03-06  1:35   ` master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569) Po Lu
2024-03-06 12:04     ` Eli Zaretskii
2024-03-06 12:35       ` Andrea Corallo
2024-03-06 16:20         ` Andrea Corallo [this message]

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=yp1sf13uybr.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=v.pupillo@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).