[
https://issues.apache.org/jira/browse/SCM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539081#comment-17539081
]
ASF GitHub Bot commented on SCM-976:
------------------------------------
michael-o commented on PR #134:
URL: https://github.com/apache/maven-scm/pull/134#issuecomment-1130550494
> > the issue summary is wrong and does not relate to the problem. Problem
is that the current call does not enforce default output and relies on default,
unmodified config.
>
> I think the commit message is fine now, so it would be the matter to sync
PR title and JIRA, right?
Yes, I'd more expect something like:
Explicitly provide a format to GitExe bla bla
or similar.
Something which shows the intent of the change. REason is that there is
exactly one default format, a user-defined format is a modified format.
> [GITEXE] Changelog does not work in current versions of git.
> ------------------------------------------------------------
>
> Key: SCM-976
> URL: https://issues.apache.org/jira/browse/SCM-976
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 2.0.0-M1
> Reporter: Niels Basjes
> Priority: Major
>
> Since a long time the headers for the output of "git whatchanged" have been
> changed, as a consequence there is no more output from this command.
> The reason is that the output of this command used to be something like this:
> {code}
> commit 2d22f2da71ef279c4759b1c09cdb8282b63f0cf6
> Author: Mark Struberg <strub...@yahoo.de>
> Date: 2007-11-24 01:10:06 +0100
> {code}
> yet currently it looks like this:
> {code}
> commit 4fc34cfa14f2e72506187b03a492ce55ed459d4c (HEAD -> master,
> origin/master, origin/HEAD)
> Author: Michael Osipov <micha...@apache.org>
> AuthorDate: 2022-01-08 21:02:12 +0100
> Commit: Michael Osipov <micha...@apache.org>
> CommitDate: 2022-01-08 21:02:12 +0100
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
