Ticket #336 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

git-XXX does not exists as 1.6.0

Reported by: Ben Owned by:
Priority: major Milestone: 0.7.9
Version: 0.7.8 Keywords: devtree
Cc: dustin

Description

git-XXX commands have been replaced by git XXX, and may be there since long time for some of them ...
Disclaimer: I installed git two hours ago to be able to run hg convert buildbot.git. So I'm far from being a git guru ...

Attachments

336.patch Download (1.5 KB) - added by Ben 5 years ago.
patch

Change History

Changed 5 years ago by Ben

patch

comment:1 Changed 5 years ago by dustin

  • Cc dustin added

comment:2 Changed 5 years ago by Ben

According to dustin, that switch (git-command to git command) is prior to 1.0 (2005), so, that would mean we only support 1.0+ version of git. That seams reasonable ...

comment:3 Changed 5 years ago by dustin

  • Status changed from new to closed
  • Resolution set to fixed

comment:4 Changed 5 years ago by dustin

  • Keywords devtree added; Git removed
  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:5 Changed 5 years ago by dustin

  • Milestone changed from undecided to 0.7.9

comment:6 Changed 5 years ago by warner

I'd like to be sure I'm understanding this ticket correctly: is the concern that e.g. /usr/bin/git-checkout will not exist in git-1.6.0 or beyond? And that the 'checkout' subcommand of the /usr/bin/git executable is the current preferred way to perform a checkout? And that the subcommand form has been available since git-1.0 ?

If so, this sounds like a good change. Just make sure the docs clearly state which versions of Git are supported (and the NEWS file should indicate whichever versions of Git we no longer support).

comment:7 Changed 5 years ago by warner

  • Status changed from reopened to closed
  • Resolution set to fixed

released in buildbot-0.7.9 . This is the right thing to do, but it would still be nice if the docs could state what range of 'git' versions we're compatible with.

Note: See TracTickets for help on using tickets.