public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/marxin/heads/sphinx-v7] (10 commits) sphinx: use proper lexers for target macros Date: Tue, 26 Jul 2022 12:49:58 +0000 (GMT) [thread overview] Message-ID: <20220726124958.9B0FD3858C83@sourceware.org> (raw) The branch 'marxin/heads/sphinx-v7' was updated to point to: 540e4c0ac85... sphinx: use proper lexers for target macros It previously pointed to: 46ee39c9592... sphinx: use proper lexers for target macros Diff: !!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST): ------------------------------------------------------------------- 46ee39c... sphinx: use proper lexers for target macros 7df0da8... sphinx,ada: port to Sphinx 60a4049... sphinx,jit: port libgccjit to shared Sphinx b48fc23... sphinx: remove texinfo files 166f109... sphinx: add tm.rst.in. a829d10... sphinx: support Sphinx in build system 89d12fd... sphinx: use tm.rst.in file in target macros 630410c... sphinx: port .def files to RST ab4aed8... sphinx: update baseconf.py file e71d6aa... sphinx: copy files from texi2rst-generated Summary of changes (added commits): ----------------------------------- 540e4c0... sphinx: use proper lexers for target macros ab99c81... sphinx,ada: port to Sphinx 74646cd... sphinx,jit: port libgccjit to shared Sphinx 5f6f9e2... sphinx: remove texinfo files 0ca0e9e... sphinx: add tm.rst.in. b14c4de... sphinx: support Sphinx in build system 853db59... sphinx: use tm.rst.in file in target macros 7972a59... sphinx: port .def files to RST 04870bb... sphinx: update baseconf.py file f83e3c9... sphinx: copy files from texi2rst-generated
next reply other threads:[~2022-07-26 12:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-26 12:49 Martin Liska [this message] 2022-07-27 12:17 Martin Liska
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=20220726124958.9B0FD3858C83@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.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: linkBe 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).