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-final] (10 commits) FIXME: use temporary Intersphinx URL.
Date: Tue,  8 Nov 2022 14:53:16 +0000 (GMT)	[thread overview]
Message-ID: <20221108145316.D1C593858432@sourceware.org> (raw)

The branch 'marxin/heads/sphinx-final' was updated to point to:

 1531973a8cf... FIXME: use temporary Intersphinx URL.

It previously pointed to:

 64d8b345eb0... FIXME: use temporary Intersphinx URL.

Diff:

!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------

  64d8b34... FIXME: use temporary Intersphinx URL.
  8b33b1d... FIXME: sphinx: add update_web_docs_git.py script
  2f635b5... sphinx: support installation if sphinx-build is missing
  f94b734... sphinx: sync latest changes
  e6e50f0... sphinx: do not use tm.rst.in with empty content
  e40bc0e... sphinx: fix cross manual references
  a3ace48... sphinx: add --with-sphinx-build
  0aadfb3... sphinx: use proper lexers for target macros
  1ed6f98... sphinx: ada: port to Sphinx
  7554ede... sphinx: jit: port libgccjit to shared Sphinx


Summary of changes (added commits):
-----------------------------------

  1531973... FIXME: use temporary Intersphinx URL.
  0028ec9... FIXME: sphinx: add update_web_docs_git.py script
  533954a... sphinx: support installation if sphinx-build is missing
  7053b69... sphinx: sync latest changes
  d2d892d... sphinx: do not use tm.rst.in with empty content
  1ebf5e4... sphinx: fix cross manual references
  f9afb17... sphinx: add --with-sphinx-build
  2bdd083... sphinx: use proper lexers for target macros
  ef1d35d... sphinx: ada: port to Sphinx
  580f76b... sphinx: jit: port libgccjit to shared Sphinx

                 reply	other threads:[~2022-11-08 14:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221108145316.D1C593858432@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: 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).