GNU bug report logs -
#64055
31.0.50; log-view-modify-change-comment support for Git and Hg
Previous Next
Full log
View this message in rfc822 format
Hello,
On Fri 18 Oct 2024 at 08:26am +03, Eli Zaretskii wrote:
> The commit log message for the changes doesn't mention the bug number;
> please always remember to do that in the future. In this case, the
> discussion leading to the change is long and significant, so including
> a pointer to it is important for future forensics.
In this case, my commits didn't add vc-git-modify-change-comment, and
most of the discussion in this bug has been about that. So, I thought
that it would be best to include the bug number in the later commit
adding vc-git-modify-change-comment, and not in any commits I've made so
far. Would you prefer that it had been included in all of them?
> More importantly, why are we installing changes in VC that are
> supported by a single backend? This is against the VC design
> principles. Let's please install soon implementations for other
> relevant backends. I think this should be very simple, but if you
> need help for some backends, feel free to ask for it.
Actually, in this case, the functionality already exists for SCCS, RCS,
CVS, SVN and Hg in log-view-extract-comment, and I was just adding
support for Git.
> Btw, since CVS has an existing command-line option to amend the log
> message of a particular commit, I wonder whether the design that goes
> through a separate backend function which extracts the comment first
> is valid.
We still need to extract the comment first so that the user has some
text to edit.
--
Sean Whitton
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.