* Re: master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569).
[not found] ` <20240305213814.AABFFC00231@vcs2.savannah.gnu.org>
@ 2024-03-06 1:35 ` Po Lu
2024-03-06 12:04 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Po Lu @ 2024-03-06 1:35 UTC (permalink / raw)
To: emacs-devel; +Cc: Vincenzo Pupillo
Andrea Corallo <acorallo@gnu.org> writes:
> branch: master
> commit d5f11e890c598cd2e15cb2fd93e604ed100ce355
> Author: Vincenzo Pupillo <v.pupillo@gmail.com>
> Commit: Andrea Corallo <acorallo@gnu.org>
>
> * Makefile.in (install-info): Fix target (bug#69569).
> ---
> Makefile.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile.in b/Makefile.in
> index d54583399d0..6f014909307 100644
> --- a/Makefile.in
> +++ b/Makefile.in
> @@ -812,7 +812,7 @@ install-info: info
> done; \
> (cd "$${thisdir}"; \
> ${INSTALL_INFO} --info-dir="$(DESTDIR)${infodir}" "$(DESTDIR)${infodir}/$$elt"); \
> - 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?
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569).
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
0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2024-03-06 12:04 UTC (permalink / raw)
To: Po Lu, Andrea Corallo; +Cc: emacs-devel, v.pupillo
> 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.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569).
2024-03-06 12:04 ` Eli Zaretskii
@ 2024-03-06 12:35 ` Andrea Corallo
2024-03-06 16:20 ` Andrea Corallo
0 siblings, 1 reply; 4+ messages in thread
From: Andrea Corallo @ 2024-03-06 12:35 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: Po Lu, emacs-devel, v.pupillo
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.
Andrea
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: master d5f11e890c5: * Makefile.in (install-info): Fix target (bug#69569).
2024-03-06 12:35 ` Andrea Corallo
@ 2024-03-06 16:20 ` Andrea Corallo
0 siblings, 0 replies; 4+ messages in thread
From: Andrea Corallo @ 2024-03-06 16:20 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: Po Lu, emacs-devel, v.pupillo
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-03-06 16:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
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.