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
Right now git-get relases two binaries: git-get and git-list. Consider building only a single git-get binary and embed the list functionality into it (eg, git get list or git get --list).
It was suggested by the creator of git-bug based on disuccions about his project on git mailing list (link to the thread).
Releasing only a single binary would reduce the "namespace grabbing" and may make more sense semantically since git list refers to repos managed by git get anyway.
The text was updated successfully, but these errors were encountered:
and for purposes of having git automagically use these for subcommands you could also check what the binary is called as. if called as git-get, act as git-get, if called as git-list, act as git-list, like busybox. Then you can have binary git-get (the name of the of the project) and symlink git-list -> git-get
Right now git-get relases two binaries:
git-get
andgit-list
. Consider building only a singlegit-get
binary and embed thelist
functionality into it (eg,git get list
orgit get --list
).It was suggested by the creator of git-bug based on disuccions about his project on git mailing list (link to the thread).
Releasing only a single binary would reduce the "namespace grabbing" and may make more sense semantically since
git list
refers to repos managed bygit get
anyway.The text was updated successfully, but these errors were encountered: