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/devel/sphinx] (2 commits) Merge branch 'master' into devel/sphinx Date: Thu, 14 Jul 2022 08:35:50 +0000 (GMT) [thread overview] Message-ID: <20220714083550.C573538582BE@sourceware.org> (raw) The branch 'devel/sphinx' was updated to point to: b8cae48643f... Merge branch 'master' into devel/sphinx It previously pointed to: 2d4ba09d237... Merge branch 'master' into devel/sphinx Diff: Summary of changes (added commits): ----------------------------------- b8cae48... Merge branch 'master' into devel/sphinx fd782de... docs: fix position of @end deftypefn (*) (*) This commit already exists in another branch. Because the reference `refs/heads/devel/sphinx' matches your hooks.email-new-commits-only configuration, no separate email is sent for this commit.
next reply other threads:[~2022-07-14 8:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-14 8:35 Martin Liska [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-09-20 12:03 Martin Liska 2022-09-05 9:22 Martin Liska 2022-07-26 12:28 Martin Liska 2022-07-14 9:34 Martin Liska 2022-06-17 11:35 Martin Liska 2021-12-28 10:14 Martin Liska 2021-12-22 11:17 Martin Liska 2021-12-22 11:08 Martin Liska 2021-06-14 14:08 Martin Liska 2021-06-14 14:05 Martin Liska 2021-05-26 7:35 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=20220714083550.C573538582BE@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).