[
https://issues.apache.org/jira/browse/SCM-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962317#comment-17962317
]
ASF GitHub Bot commented on SCM-625:
------------------------------------
jira-importer commented on issue #839:
URL: https://github.com/apache/maven-scm/issues/839#issuecomment-2964626936
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> AbstractCvsStatusCommand should use 'cvs status' instead of 'cvs update'
> ------------------------------------------------------------------------
>
> Key: SCM-625
> URL: https://issues.apache.org/jira/browse/SCM-625
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.5
> Reporter: Mark Struberg
> Priority: Major
>
> AbstractCvsStatusCommand should use 'cvs status' instead of 'cvs update'
> cvs update is pretty evil since it will also fetch any changes available in
> the upstream repo.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
