From: "Shawn O. Pearce" <spearce@spearce.org>
To: Stefano Spinucci <virgo977virgo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git docs on kernel.org too new?
Date: Thu, 1 Feb 2007 14:20:57 -0500 [thread overview]
Message-ID: <20070201192057.GC18608@spearce.org> (raw)
In-Reply-To: <906f26060702011014r254ffd5frd75296c8443078ab@mail.gmail.com>
Stefano Spinucci <virgo977virgo@gmail.com> wrote:
> this isn't the first time someone is confused by git docs, and I guess
> why we can't have a documentation page as
> http://www.python.org/doc/versions/
Indeed. Or at least only post docs which correspond to a
downloadable tar file?
Perhaps we could embed in at least the HTML version of the docs the
output of `GIT-VERSION-GEN` ? Then users at least have a chance
at knowing the docs are referring to 1.5.0-rc3 and not to 1.4.4.4?
--
Shawn.
next prev parent reply other threads:[~2007-02-01 19:21 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 [this message]
2007-02-01 19:17 ` Shawn O. Pearce
2007-02-01 19:21 ` Brandon Casey
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=20070201192057.GC18608@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=virgo977virgo@gmail.com \
/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).