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
{{ message }}
This repository was archived by the owner on Aug 7, 2025. It is now read-only.
Would be great to have version info about autospec/common #7
@bktan8 I am thinking that the common tooling should support doing a "fetch" operation to retrieve the latest state of common, autospec, etc and possibly all package repos.
A new command like make versionstatus could then compare the state of the local repos with the remote repos.
Let's say you ran a make pull at some point, then two weeks later, you want to know how far behind you are. Then perhaps you could do:
$ make versionstatus
*** Repos up-to-date. Run make fetch [REPO=<name>] to retrieve latest repo state
$ make fetch REPO=projects/common
$ make versionstatus
projects/common is 45 commits behind
$ make pull-projects/common
...
Maybe a versiondiff command would also be helpful to inspect the diff between local and remote branches?
Activity
bryteise commentedon Jul 12, 2018
Version of what? Clear Linux?
bktan8 commentedon Jul 12, 2018
autospec / common tooling
i just want to know if i'm behind or not.
bryteise commentedon Jul 12, 2018
Those aren't versioned. make pull will update them though.
phmccarty commentedon Jul 24, 2018
@bktan8 I am thinking that the common tooling should support doing a "fetch" operation to retrieve the latest state of common, autospec, etc and possibly all package repos.
A new command like
make versionstatuscould then compare the state of the local repos with the remote repos.Let's say you ran a
make pullat some point, then two weeks later, you want to know how far behind you are. Then perhaps you could do:Maybe a
versiondiffcommand would also be helpful to inspect the diff between local and remote branches?