git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Casey <casey@nrlssc.navy.mil>
To: git@vger.kernel.org
Subject: Re: git docs on kernel.org too new?
Date: Thu, 1 Feb 2007 13:21:50 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0702011319590.31498@torch.nrlssc.navy.mil> (raw)
In-Reply-To: <20070201191747.GB18608@spearce.org>

On Thu, 1 Feb 2007, Shawn O. Pearce wrote:

> Brandon Casey <casey@nrlssc.navy.mil> wrote:
>> The git documentation here:
>>
>>   http://www.kernel.org/pub/software/scm/git/docs/
>>
>> does not seem to describe the current stable release of
>> git: git-1.4.4.4 (there is a release candidate of 1.5.0 on kernel.org)
>
> Yes.  The docs on kernel.org roughly track the `master` branch
> of git.git, which is stablizing the 1.5.0 release.  Git 1.5.0-rc3
> was posted last night, and with the exception of a couple of minor
> cleanups for the detached HEAD warning messages, will be the 1.5.0
> final release.

Ah. I thought you might be doing something clever like that.

> Despite being a release candidate I think we would all encourage
> you to try working with 1.5.0-rc3 or later.  It is extremely stable,
> the documentation has been significantly improved and updated since
> 1.4.4.4, and the learning curve should be easier for new users.

will do, thanks.

-brandon

      reply	other threads:[~2007-02-01 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 17:26 git docs on kernel.org too new? Brandon Casey
2007-02-01 18:14 ` Stefano Spinucci
2007-02-01 19:20   ` Shawn O. Pearce
2007-02-01 19:17 ` Shawn O. Pearce
2007-02-01 19:21   ` Brandon Casey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.62.0702011319590.31498@torch.nrlssc.navy.mil \
    --to=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).