This is the mail archive of the
mailing list for the GCC project.
Re: Fixing gcc git logs
On 1/2/20 11:49 AM, Richard Earnshaw wrote:
On 02/01/2020 02:00, Jerry wrote:
In the following git log entry, I made a typo on the PR number in the
libgfortran ChangeLog file. I noticed this right after the git commit,
while editing the git log.
If you've pushed the branch to a public tree then it might be too late,
depending on the push policy for branches (in gcc trunk we will not
permit rewriting history in that way because it breaks other users
trying to pull). Some more private branches might permit such rewriting
I am glad you explained it. Previously, the only reaction I got from
git-cognoscenti was "Don't do that - it will ruin history for everybody!".
Thanks ! Might 2020 be the year of git for GCC.
Toon Moene - e-mail: email@example.com - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news