[
https://issues.apache.org/jira/browse/SCM-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959904#comment-17959904
]
ASF GitHub Bot commented on SCM-21:
-----------------------------------
jira-importer opened a new issue, #270:
URL: https://github.com/apache/maven-scm/issues/270
**[Brett
Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)**
opened
**[SCM-21](https://issues.apache.org/jira/browse/SCM-21?redirect=false)** and
commented
while in CVS revision# and tag are handled in the same way, the concepts can
be separated and will make other SCMs easier.
for example, in subversion, valid revisions are:
rev#
HEAD
BASE
COMMITTED
PREV
{DATE}
tags are normal checkouts from a different base.
In CVS, revisions are:
rev# (per file only really makes sense here, but can apply to several)
HEAD
SOME_BRANCH_TAG
{DATE}
---
1 votes, 0 watchers
> separate revision and tag handling
> ----------------------------------
>
> Key: SCM-21
> URL: https://issues.apache.org/jira/browse/SCM-21
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-api
> Reporter: Brett Porter
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-rc1
>
>
> while in CVS revision# and tag are handled in the same way, the concepts can
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
