4 ms·
Personally I think it just needs a 3.0 where they completely rename all the commands so that they're really unified. I know there was pushback on this in the pa
by grogenaut 5y ago
Personally I think it just needs a 3.0 where they completely rename all the commands so that they're really unified. I know there was pushback on this in the past
- seoaeu 5y agoThe thing with command line interfaces is that since the same interface is used by humans and computer scripts, you essentially end up with an unversioned API that you can never make breaking changes to.
- symlinkk 5y agoIt is versioned. There is git —-version. If your scripts break with the new version, don’t upgrade.
- seoaeu 5y agoWith other sorts of APIs you are given the choice between say the v1 version or the v2 version, with both endpoints being available at the same time. However, when it comes to command line programs for all practical purposes you can only have a single version installed at a time. And it of course doesn't help that essentially none of the existing scripts even check the versions of the software they run.
- grogenaut 5y agoThis is easily fixable with a new command or envvar. This happens all the time
- matheusmoreira 5y agoThat would be nice but will probably never happen due to backwards compatibility. Breaking changes in git would be even worse than the slow switch to Python 3.
- lanstin 5y agoJust call the consistent one "ggit" and the inconsistent one "git."