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
At one time, we had a separate version command that would report the versions of Pinto, Pinto::Remote and Pinto::Server. These were shipped separately so it was quite possible for each to have a different $VERSION.
But then I decided to ship all those modules in one distribution and give them the same $VERSION. At that point, I removed the version command and just relied on the built-in --version option that App::Cmd provides.
However, neither one of those would tell you what version of the code is running on a remote server, which is very useful to know when reporting bugs or trying to diagnose one.
The text was updated successfully, but these errors were encountered:
At one time, we had a separate
version
command that would report the versions of Pinto, Pinto::Remote and Pinto::Server. These were shipped separately so it was quite possible for each to have a different $VERSION.But then I decided to ship all those modules in one distribution and give them the same $VERSION. At that point, I removed the
version
command and just relied on the built-in--version
option that App::Cmd provides.However, neither one of those would tell you what version of the code is running on a remote server, which is very useful to know when reporting bugs or trying to diagnose one.
The text was updated successfully, but these errors were encountered: