Re: commit 9d0f14

[sfeam <sf...@us...>]

On Thursday, 22 March 2018 04:04:26 Mojca Miklavec wrote:
> On 22 March 2018 at 03:39, sfeam via gnuplot-beta wrote:
> >
> > I wish there was a way to edit commit messages afterwards.
> > That is the thing I dislike the about about git so far.
> > You cannot go back and fix typos or errors in the commit
> > messages.
> 
> You can.
> 
> "git commit --amend" for the latest message
> "git rebase -i HEAD~<N>" for <N> latest commits
> 
> You can arbitrarily use these before pushing the changes to the
> server. Once they are on the server you can still do this (with force
> pushing)

I know you can do it locally, but it does not work once it
has been pushed to SourceForge.  The --amend and --force
modifiers are rejected on the SourceForge end.

> , but you may cause inconvenience to other users who might
> have synced the sources in the meantime, so it's not recommended.

I can understand how it might cause an inconvenience if the
change was made retrospectively to the source file itself,
but I fail to see a problem from correcting an error in the
commit message.

If I get annoyed enough I may think harder about moving the main
repository off SourceForge.   The remote interface is very clunky.

	Ethan

 
> Mojca