This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
broken svn commit logs and how to fix them
- From: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
- To: "GCC Development" <gcc at gcc dot gnu dot org>
- Cc: pault at gcc dot gnu dot org, "Doug Gregor" <doug dot gregor at gmail dot com>, "Andrew Pinski" <pinskia at gcc dot gnu dot org>, "Jakub Jelinek" <jakub at redhat dot com>, "Michael Meissner" <gnu at the-meissners dot org>, "Jan Hubicka" <jh at suse dot cz>
- Date: Tue, 26 Aug 2008 16:47:57 +0200
- Subject: broken svn commit logs and how to fix them
Dear all,
If you mess up a commit log, not everything is lost. You can edit the
commit log of a particular revision by doing:
svn propedit -r REVISION --revprop svn:log
Note that this change is not versioned: whatever was the log before is
completely overwritten by the new one.
I have fixed the log of revision 138275, which was a diff dump until a
moment ago, with the correct one.
Some more broken commits logs follow. Please fix them:
revision committer problem
129905 dgregor a diff
129888 pinskia a diff
139317 jakub the commit log mentions files that were not committed
138154 meissner this should mention the files modified
138141 hubicka this should mention the files modified
138140 hubicka the commit log mentions changes that were not committed
If you spot an obviously wrong commit log message, please fix it
yourself or bug the committer to fix it.
Thanks,
Manuel.