[
https://issues.apache.org/jira/browse/SCM-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962541#comment-17962541
]
ASF GitHub Bot commented on SCM-681:
------------------------------------
jira-importer commented on issue #889:
URL: https://github.com/apache/maven-scm/issues/889#issuecomment-2964631422
**[Jorge
Costa](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jmecosta)**
commented
Hi Olivier,
I was looking into the implementation of this feature, and at least for git
i found difficult to understand how the parameter is passed to the command
executor.
This is the implementation of the command:
Commandline cl = createCommandLine( workingDirectory.getBasedir(),
filename,
parameters.getBoolean(
CommandParameter.IGNORE_WHITESPACE, false ) );
As i understand in the new BlameScmRequest is only setting an internal
boolean ignoreWhitespace to true and not the property. So i see that the ignore
whitespaces is always ignored.
Is this the intended implementation, or am i not seeing everything?
Thanks in advance
Br,
Jorge Costa
> Git blame fails to report line authors on windows with core.autocrlf = true
> ---------------------------------------------------------------------------
>
> Key: SCM-681
> URL: https://issues.apache.org/jira/browse/SCM-681
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.7
> Environment: Windows
> git configured with core.autocrlf = true
> Reporter: David Gageot
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.9
>
>
> Git blame cannot report line authors when each line is modified locally by
> the autocrlf parameter. It thinks every line is Not Yet Committed.
> The fix is to use git blame -w instead of plain git blame, to ignore
> whitespaces.
> See discussion here:
> http://stackoverflow.com/questions/4638500/git-blame-showing-no-history
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
