All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: git-scm pages deliver outdated Git docs
Date: Fri, 1 Sep 2017 23:10:32 +0100	[thread overview]
Message-ID: <6133C06F-D17F-442C-B68E-18DE4BC470E8@gmail.com> (raw)
In-Reply-To: <20170831183734.6sukpdpvi23h3d7v@sigill.intra.peff.net>


> On 31 Aug 2017, at 19:37, Jeff King <peff@peff.net> wrote:
> 
> On Thu, Aug 31, 2017 at 09:28:35AM +0100, Lars Schneider wrote:
> 
>> looks like the git-scm pages deliver outdated Git docs (v2.13.1):
>> https://git-scm.com/docs/git
>> 
>> Is this intentional? If not, who should be contacted?
> 
> The docs are up-to-date (and a cron job keeps them updated when there
> are new releases). I think the issue is just one of presentation. That
> manpage in particular hasn't been updated since v2.13.1, so that's the
> highest field in the version dropdown. If you switch to:
> 
>  https://git-scm.com/docs/git-status
> 
> for instance, you'll see "v2.14.0 | git-status last updated in 2.14.0".
> It's actually sucked in v2.14.1 (you can tell because that's what's
> mentioned as the latest version on the front page), but there were no
> manpages updated between v2.14.0 and v2.14.1.
> 
> So I think all is working as intended, though there may be room for
> improvement in the text used at the top.
> 

Thanks for the explanation!

- Lars


      reply	other threads:[~2017-09-01 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31  8:28 git-scm pages deliver outdated Git docs Lars Schneider
2017-08-31 18:37 ` Jeff King
2017-09-01 22:10   ` Lars Schneider [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=6133C06F-D17F-442C-B68E-18DE4BC470E8@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.