GNU bug report logs -
#64055
31.0.50; log-view-modify-change-comment support for Git and Hg
Previous Next
Full log
Message #20 received at 64055 <at> debbugs.gnu.org (full text, mbox):
>>>>> On Wed, 14 Jun 2023 09:54:20 -0400, Morgan Smith <Morgan.J.Smith <at> outlook.com> said:
Morgan> Robert Pluim <rpluim <at> gmail.com> writes:
>> Yes, eg magitʼs interactive rebase is great for that kind of stuff. I donʼt
>> know offhand if it uses autosquash.
Morgan> I look briefly at their code and they use a perl wrapper around the
Morgan> interactive rebase. I suppose that's another way of doing it. I don't
Morgan> think it's any better or worse then my approach though.
OK
>>
Morgan> 'git commit --amend' is actually already built into the Emacs vc system
Morgan> and works great. I don't think you can use it without a diff though.
>>
>> Fixing that would fit 99.99% of the cases where I want to reword a
>> commit message, and I suspect Iʼm not alone.
Morgan> Strange. I'm usually working on at least a couple commits at a time.
Morgan> For example, if I'm working on a change and I notice a typo in a
Morgan> docstring unrelated to my change then I'll stick that into a commit.
Morgan> Then I'll fix up all my commit messages at the end of my session.
That kind of thing I just leave in, and if it gets in the way Iʼll
stash it, and then commit it afterwards. But then again, for Emacs I
try not to have too many commits in flight at the same time. To each
their own.
Morgan> Regardless, the current amend logic is great if you need to amend code
Morgan> changes. For the case without a diff, you could simply use the feature
Morgan> I'm adding here.
Right
Robert
--
This bug report was last modified 104 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.