Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Git as another VCS backend #193

Open
ermshiperete opened this issue Sep 26, 2019 · 1 comment
Open

Implement Git as another VCS backend #193

ermshiperete opened this issue Sep 26, 2019 · 1 comment

Comments

@ermshiperete
Copy link
Member

This depends on #192.

@rmunn
Copy link
Contributor

rmunn commented Dec 16, 2023

One issue is that we use branch names to track FLEx model versions, e.g. 7500002.7000072. In Mercurial, each commit is associated with a branch, so "which branch is this commit from" is part of the Mercurial data model and is easy to retrieve. In Git, commits do not know which branch they're on, and it may be more difficult to work out which commit belongs to which branch: we'd have to start with the various branch heads and work backwards through their parent chains to assign branch IDs to revisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants