{"thread":{"id":"6611","subject":"git docs on kernel.org too new?","startedAt":"2007-02-01T17:26:49Z","lastAt":"2007-02-01T19:21:50Z","messageCount":5,"participants":["Brandon Casey","Stefano Spinucci","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"33264","messageId":"Pine.LNX.4.62.0702011051300.31498@torch.nrlssc.navy.mil","threadId":"6611","inReplyTo":null,"subject":"git docs on kernel.org too new?","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2007-02-01T17:26:49Z","receivedAt":"2007-02-01T17:26:49Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"\n\nThe git documentation here:\n\n   http://www.kernel.org/pub/software/scm/git/docs/\n\ndoes not seem to describe the current stable release of\ngit: git-1.4.4.4 (there is a release candidate of 1.5.0 on kernel.org)\n\nI just want to let you know that it has been making it difficult to\nlearn how to use git.\n\nI think in some cases the documentation is out of date, but I suspect\nthat in other cases the documentation refers to the future 1.5.0 release?\n\nFor example:\n\n-Step one of tutorial.html:\n\n    $ git config --global user.name \"Your Name Comes Here\"\n\n    But git-config does not exist.\n\n-Step two of tutorial \"Importing a new project\"\n\n    $ git init\n\n    But git-init does not exist.\n\n-git-remote does not exist.\n\n-Later \"$ git merge experimental\" is suggested, but see below, this\n  appears to be the wrong usage.\n\n-The everyday.html and git-merge.html pages describe\n   a different usage for git-merge than the git-1.4.4.4 docs and\n   executables.\n\n   everyday.html(kernel.org):\n     $ git checkout master (9)\n     $ git merge alsa-audio (10)\n\n   git-merge(kernel.org):\n     git-merge [-n] [--no-commit] [--squash] [-s <strategy>] -m=<msg> <remote> <remote>\n\n   git-merge(1.4.4.4):\n     Usage: git-merge [-n] [--no-commit] [--squash] [-s <strategy>]... <merge-message> <head> <remote>+\n\n\n-brandon\n"},{"id":"33266","messageId":"906f26060702011014r254ffd5frd75296c8443078ab@mail.gmail.com","threadId":"6611","inReplyTo":"Pine.LNX.4.62.0702011051300.31498@torch.nrlssc.navy.mil","subject":"Re: git docs on kernel.org too new?","fromName":"Stefano Spinucci","fromEmail":"virgo977virgo@gmail.com","sentAt":"2007-02-01T18:14:26Z","receivedAt":"2007-02-01T18:14:26Z","isPatch":false,"sender":{"key":"virgo977virgo@gmail.com","avatar":null},"body":"this isn't the first time someone is confused by git docs, and I guess\nwhy we can't have a documentation page as\nhttp://www.python.org/doc/versions/\n\n---\nStefano Spinucci\n"},{"id":"33270","messageId":"20070201191747.GB18608@spearce.org","threadId":"6611","inReplyTo":"Pine.LNX.4.62.0702011051300.31498@torch.nrlssc.navy.mil","subject":"Re: git docs on kernel.org too new?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-02-01T19:17:47Z","receivedAt":"2007-02-01T19:17:47Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Brandon Casey <casey@nrlssc.navy.mil> wrote:\n> The git documentation here:\n> \n>   http://www.kernel.org/pub/software/scm/git/docs/\n> \n> does not seem to describe the current stable release of\n> git: git-1.4.4.4 (there is a release candidate of 1.5.0 on kernel.org)\n\nYes.  The docs on kernel.org roughly track the `master` branch\nof git.git, which is stablizing the 1.5.0 release.  Git 1.5.0-rc3\nwas posted last night, and with the exception of a couple of minor\ncleanups for the detached HEAD warning messages, will be the 1.5.0\nfinal release.\n\nDespite being a release candidate I think we would all encourage\nyou to try working with 1.5.0-rc3 or later.  It is extremely stable,\nthe documentation has been significantly improved and updated since\n1.4.4.4, and the learning curve should be easier for new users.\n\n-- \nShawn.\n"},{"id":"33271","messageId":"20070201192057.GC18608@spearce.org","threadId":"6611","inReplyTo":"906f26060702011014r254ffd5frd75296c8443078ab@mail.gmail.com","subject":"Re: git docs on kernel.org too new?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-02-01T19:20:57Z","receivedAt":"2007-02-01T19:20:57Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Stefano Spinucci <virgo977virgo@gmail.com> wrote:\n> this isn't the first time someone is confused by git docs, and I guess\n> why we can't have a documentation page as\n> http://www.python.org/doc/versions/\n\nIndeed.  Or at least only post docs which correspond to a\ndownloadable tar file?\n\nPerhaps we could embed in at least the HTML version of the docs the\noutput of `GIT-VERSION-GEN` ?  Then users at least have a chance\nat knowing the docs are referring to 1.5.0-rc3 and not to 1.4.4.4?\n\n-- \nShawn.\n"},{"id":"33272","messageId":"Pine.LNX.4.62.0702011319590.31498@torch.nrlssc.navy.mil","threadId":"6611","inReplyTo":"20070201191747.GB18608@spearce.org","subject":"Re: git docs on kernel.org too new?","fromName":"Brandon Casey","fromEmail":"casey@nrlssc.navy.mil","sentAt":"2007-02-01T19:21:50Z","receivedAt":"2007-02-01T19:21:50Z","isPatch":false,"sender":{"key":"drafnel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/921167?v=4"},"body":"On Thu, 1 Feb 2007, Shawn O. Pearce wrote:\n\n> Brandon Casey <casey@nrlssc.navy.mil> wrote:\n>> The git documentation here:\n>>\n>>   http://www.kernel.org/pub/software/scm/git/docs/\n>>\n>> does not seem to describe the current stable release of\n>> git: git-1.4.4.4 (there is a release candidate of 1.5.0 on kernel.org)\n>\n> Yes.  The docs on kernel.org roughly track the `master` branch\n> of git.git, which is stablizing the 1.5.0 release.  Git 1.5.0-rc3\n> was posted last night, and with the exception of a couple of minor\n> cleanups for the detached HEAD warning messages, will be the 1.5.0\n> final release.\n\nAh. I thought you might be doing something clever like that.\n\n> Despite being a release candidate I think we would all encourage\n> you to try working with 1.5.0-rc3 or later.  It is extremely stable,\n> the documentation has been significantly improved and updated since\n> 1.4.4.4, and the learning curve should be easier for new users.\n\nwill do, thanks.\n\n-brandon\n"}]}