This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

1-800-GIT-HELP: Fixing a commit message?


It turns out I fumbled the commit message on the commit below to wwwdocs.

Instead of 
    Redirect cvswrite.html to gitwrite.html instead of svnwrite.html.
I committed this with a message of 
    Redirect cvs.html to git.html instead of svn.html.
and pushed already.

In CVS I could manually edit the ,v files; in SVN I believe we did
not want to allow for fixing commit messages a posteriori -- how 
about our Git setup?  Policy-wise and practically?

Gerald

====== from gcc-patches ======
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Date: Thu, 16 Jan 2020 19:15:28 +0100 (CET)
Subject: [PATCH] Redirect cvswrite.html to gitwrite.html instead of svnwrite.html.

I doubt there's many references to https://gcc.gnu.org/cvs.html 
left, but just in case - Git is the new SVN is the new CVS. :-)

Gerald
---
 htdocs/.htaccess | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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
-- 
2.24.1


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]