Re: How do I fix a typo in a git commit comment?

Mark Atwood via devel : > We can accumulate a list of typos and gltiches in the history. We will > wait until something major, or it gets long enough, and then we can fix > them all in one force push. I've done this on my projects. A lot of typos got fixed when the GPSD repo moved off Savannah.

Re: How do I fix a typo in a git commit comment?

Hal Murray : > If nothing else, we should document the issues. A reference to this > discussion might be appropriate. Do we have a FAQ type place to collect > things like this? No. This is general git knowledge, not a project-specific issue. > How messy is it for people who have cloned/pulle

Re: How do I fix a typo in a git commit comment?

We can accumulate a list of typos and gltiches in the history. We will wait until something major, or it gets long enough, and then we can fix them all in one force push. In the meantime, for this typo, code up adding a comment to the relevant code about the typo, then commit the change with a c

Re: How do I fix a typo in a git commit comment?

rlaa...@wiktel.com said: >> Are there any alternatives? > See `git notes` to attach notes to objects (e.g. > commits) after the fact without changing the object itself. > Using the example from the man page, try something like this: > git notes add -m 'The 674 should be 474.' c8c888f8 Thanks.

Re: How do I fix a typo in a git commit comment?

On 03/25/2018 03:56 AM, Hal Murray via devel wrote: > How messy is it for people who have cloned/pulled to recover? I think that's > the key issue. Is this a good time for a trial run? If you catch it right away, you might get away with it, but in general, don't. > Are there any alternatives?

Re: How do I fix a typo in a git commit comment?

e...@thyrsus.com said: > If it weren't in the public repo this would be easy - I'm enclosing a script > that does this. > Since it is, I'd have to edit it here, then unprotect the public master > branch, then force-push, then reprotect it. This will take the public repo > temporarily out of servi

Re: How do I fix a typo in a git commit comment?

Hal Murray via devel : > > The 674 should be 474. > > commit c8c888f8f2ef295c0ea5f854127069b3812e4c09 > Author: Hal Murray > Date: Fri Mar 23 01:11:17 2018 -0700 > > Add logging of year(s) on large clock steps. Issue #674 If it weren't in the public repo this would be easy - I'm enclosi