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] Remove man-related directives.
Date: Wed,  2 Jun 2021 12:46:50 +0000 (GMT)	[thread overview]
Message-ID: <20210602124650.F23DC383303B@sourceware.org> (raw)

https://gcc.gnu.org/g:fcea5603e57e3f8c17ca259f36bd92c0e0bd8f35

commit fcea5603e57e3f8c17ca259f36bd92c0e0bd8f35
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Jun 2 14:45:49 2021 +0200

    Remove man-related directives.

Diff:
---
 gcc/doc/include/funding.texi | 18 ------------------
 1 file changed, 18 deletions(-)

diff --git a/gcc/doc/include/funding.texi b/gcc/doc/include/funding.texi
index d1583fabc0d..f138b1b670e 100644
--- a/gcc/doc/include/funding.texi
+++ b/gcc/doc/include/funding.texi
@@ -1,13 +1,4 @@
-@ignore
-@c Set file name and title for man page.
-@setfilename fsf-funding
-@settitle Funding Free Software
-@c man begin SEEALSO
-gpl(7), gfdl(7).
-@c man end
-@end ignore
 @node Funding
-@c man begin DESCRIPTION
 @unnumbered Funding Free Software
 
 If you want to have more free software a few years from now, it makes
@@ -49,12 +40,3 @@ major new features or packages contribute the most.
 By establishing the idea that supporting further development is ``the
 proper thing to do'' when distributing free software for a fee, we can
 assure a steady flow of resources into making more free software.
-@c man end
-
-@display
-@c man begin COPYRIGHT
-Copyright @copyright{} 1994 Free Software Foundation, Inc.
-Verbatim copying and redistribution of this section is permitted
-without royalty; alteration is not permitted.
-@c man end
-@end display


                 reply	other threads:[~2021-06-02 12:46 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=20210602124650.F23DC383303B@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).