Git undo: We can do better

Re:Git undo: We can do better by grogenaut on Monday June 21, 2021 @12:06PM (#27580520)

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

[ Parent | on HN ]

Re:Git undo: We can do better by seoaeu on Monday June 21, 2021 @01:26PM (#27581374)

The 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.

[ Parent | on HN ]

Re:Git undo: We can do better by symlinkk on Monday June 21, 2021 @05:20PM (#27584667)

It is versioned. There is git —-version. If your scripts break with the new version, don’t upgrade.

[ Parent | on HN ]

Re:Git undo: We can do better by seoaeu on Monday June 21, 2021 @10:08PM (#27587202)

With 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.

[ Parent | on HN ]

Re:Git undo: We can do better by grogenaut on Tuesday June 22, 2021 @01:18PM (#27594380)

This is easily fixable with a new command or envvar.

This happens all the time

[ Parent | on HN ]

Re:Git undo: We can do better by matheusmoreira on Monday June 21, 2021 @01:27PM (#27581382)

That 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.

[ Parent | on HN ]

Re:Git undo: We can do better by lanstin on Monday June 21, 2021 @02:19PM (#27582020)

Just call the consistent one "ggit" and the inconsistent one "git."

[ Parent | on HN ]