Re: Fixing gcc git logs

2020-01-02 Thread Jonathan Wakely
On Thu, 2 Jan 2020 at 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. > > So I quit the edit without saving and git reported that the commit was > abo

Re: Fixing gcc git logs

2020-01-02 Thread Toon Moene
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

Re: Fixing gcc git logs

2020-01-02 Thread Richard Earnshaw
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. > > So I quit the edit without saving and git reported that the commit was > aborted. > >

Re: Fixing gcc git logs

2020-01-02 Thread Janne Blomqvist
On Thu, Jan 2, 2020 at 4:00 AM 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. > > So I quit the edit without saving and git reported that the commit was > a

Fixing gcc git logs

2020-01-01 Thread Jerry
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. So I quit the edit without saving and git reported that the commit was aborted. Then I edited the my local ChangeLog file, d