Ticket #336 (closed defect: fixed)

Opened 3 months ago

Last modified 2 months ago

git-XXX does not exists as 1.6.0

Reported by: Ben Assigned to:
Priority: major Milestone: 0.7.9
Component: vc-support 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 (1.5 kB) - added by Ben on 08/18/08 15:07:29.
patch

Change History

08/18/08 15:07:29 changed by Ben

  • attachment 336.patch added.

patch

08/18/08 15:08:21 changed by dustin

  • cc set to dustin.

08/18/08 15:31:13 changed 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 ...

08/19/08 12:58:14 changed by dustin

  • status changed from new to closed.
  • resolution set to fixed.

http://repo.or.cz/w/buildbot.git?a=shortlog;h=refs/remotes/dustin/bug336

08/30/08 13:17:01 changed by dustin

  • keywords changed from Git to devtree.
  • status changed from closed to reopened.
  • resolution deleted.

08/30/08 14:30:46 changed by dustin

  • milestone changed from undecided to 0.7.9.

09/03/08 15:21:21 changed 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).

09/16/08 11:50:05 changed 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.