You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Repository.get_changeset accepts revision number (given as integer) which is generally wrong for both hg and git.
Mercurial can operate rather easily with that however for instance one may push repository to the server on which vcs process repositories management, then tries to use i.e. 10 as changeset id and gets different results from local repository. With integers there are integrity problems and only full hexes identifies changesets properly.
Git doesn't support integers as id numbers for commits in any way (there are some possibility to write own script but it would works properly only for new repositories which is not the case mainly).
That said, we should deprecate integer identification. This is great feature but it just is not proper one for repository management/browsing.
Applications should implement such feature on its own.
Currently Repository.get_changeset accepts revision number (given as integer) which is generally wrong for both hg and git.
Mercurial can operate rather easily with that however for instance one may push repository to the server on which vcs process repositories management, then tries to use i.e. 10 as changeset id and gets different results from local repository. With integers there are integrity problems and only full hexes identifies changesets properly.
Git doesn't support integers as id numbers for commits in any way (there are some possibility to write own script but it would works properly only for new repositories which is not the case mainly).
That said, we should deprecate integer identification. This is great feature but it just is not proper one for repository management/browsing.
Applications should implement such feature on its own.
Reference: https://bitbucket.org/marcinkuzminski/vcs/issues/43/
The text was updated successfully, but these errors were encountered: