public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arthur Cohen <arthur.cohen@embecosm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
	gcc-patches@gcc.gnu.org, herron.philip@googlemail.com
Subject: Re: [PATCH] rust: Add rust.install-dvi and rust.install-html rules
Date: Mon, 29 Apr 2024 15:24:50 +0200	[thread overview]
Message-ID: <e00440ba-190d-48af-b1e3-fd3485802e17@embecosm.com> (raw)
In-Reply-To: <20240404162719.3737066-1-christophe.lyon@linaro.org>

Thanks Christophe!

I've added your patch as part of a documentation pull-request I'm adding 
to our dev repo: https://github.com/Rust-GCC/gccrs/pull/2966

It'll be upstreamed with the next batch of commits we send, as soon as 
trunk reopens fully for 15.1.

Best,

Arthur

On 4/4/24 18:27, Christophe Lyon wrote:
> rust has the (empty) rust.dvi and rust.html rules, but lacks the
> (empty) rust.install-dvi and rust.install-html ones.
> 
> 2024-04-04  Christophe Lyon  <christophe.lyon@linaro.org>
> 
> 	gcc/rust/
> 	* Make-lang.in (rust.install-dvi, rust.install-html): New rules.
> ---
>   gcc/rust/Make-lang.in | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/gcc/rust/Make-lang.in b/gcc/rust/Make-lang.in
> index 4d646018792..4d73412739d 100644
> --- a/gcc/rust/Make-lang.in
> +++ b/gcc/rust/Make-lang.in
> @@ -342,6 +342,8 @@ selftest-rust-valgrind: $(RUST_SELFTEST_DEPS)
>   # should have dependencies on info files that should be installed.
>   rust.install-info:
>   
> +rust.install-dvi:
> +rust.install-html:
>   rust.install-pdf:
>   
>   # Install man pages for the front end. This target should ignore errors.

  parent reply	other threads:[~2024-04-29 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 16:27 Christophe Lyon
2024-04-08 21:26 ` Thomas Schwinge
2024-04-29 13:24 ` Arthur Cohen [this message]
2024-04-29 13:30   ` Christophe Lyon
2024-05-02 12:54     ` Arthur Cohen

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=e00440ba-190d-48af-b1e3-fd3485802e17@embecosm.com \
    --to=arthur.cohen@embecosm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=herron.philip@googlemail.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.
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).