public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. b45940f0b3841bc286fd18ffd312a9e297b2859c Date: Thu, 16 Jan 2020 18:05:00 -0000 [thread overview] Message-ID: <20200116180526.63721.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via b45940f0b3841bc286fd18ffd312a9e297b2859c (commit) from a17d3d8d08ea2ef78b9ee9f7ef80b127a8c078dc (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit b45940f0b3841bc286fd18ffd312a9e297b2859c Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Jan 16 19:02:53 2020 +0100 Redirect cvs.html to git.html instead of svn.html. diff --git a/htdocs/.htaccess b/htdocs/.htaccess index acaac093..a28af129 100644 --- a/htdocs/.htaccess +++ b/htdocs/.htaccess @@ -58,7 +58,7 @@ Redirect permanent /java/ https://gcc.gnu.org/ Redirect permanent /bugs.html https://gcc.gnu.org/bugs/ Redirect permanent /c9xstatus.html https://gcc.gnu.org/c99status.html -Redirect permanent /cvswrite.html https://gcc.gnu.org/svnwrite.html +Redirect permanent /cvswrite.html https://gcc.gnu.org/gitwrite.html Redirect permanent /gnats.html https://gcc.gnu.org/bugs/ Redirect permanent /proj-bp.html https://gcc.gnu.org/projects/bp/main.html Redirect permanent /proj-cpplib.html https://gcc.gnu.org/projects/cpplib.html ----------------------------------------------------------------------- Summary of changes: htdocs/.htaccess | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-16 18:05 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=20200116180526.63721.qmail@sourceware.org \ --to=gerald@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@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).