-
Notifications
You must be signed in to change notification settings - Fork 64
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
Missing git tag info? #4
Comments
I only exported the code, I can push tags as well, but our bios builds and upstream tags do not align well as there is some overlap. |
OK. I agree on not managing the upstream tags on this downstream repository. So, maybe you are managing the downstream, this repository specific tags used on your bios builds, right? I have no experience of developing a firmware. So, I might be wrong. But I suppose that the downstream specific git tags are useful to know the code or commits included in a BIOS version. You might use a downstream unique version string such as " |
I'm not certain there's value in any of the upstream tags, honestly. Having tags that align with Framework's releases are the ones that matter, so we can try use a specific release version with one tweak rather than a between-release repo state + that tweak. |
I noticed this repository doesn't have any tag info.
I can see the tag info on the upstream chromium ec repository.
I expected there are the tags "v3.2", "v3.6", "v3.7" used to ship BIOS version 3.02, 3.06, 3.07 and etc on this repository. Is the missing git tag info intentional?
The text was updated successfully, but these errors were encountered: