Re: old git reference manuals & release notes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Neal Kreitzinger" <neal@xxxxxxxx> writes:

> Before the git-scm.com link to the reference manual went down last month, 
> the reference manual used to list the links to the manuals for all the major 
> git versions and the release notes for all git versions.  This made it easy 
> to review release notes and manuals.  Now the link only shows the latest git 
> manual.  Is there a way I can access older manuals and release notes?

The HTML version of git documentation pages k.org used to serve were
specifically formatted to be served at that site, and sadly it is not
likely they will return anytime soon.

The k.org site kept these files under /pub/software/scm/git/docs/. The
in-development "master" version of pages were placed directly underneath
that directory, and the documentation pages for older versions were kept
in vX.Y.Z subdirectory of that directory.

The "master" version of the documents were formatted with a special macro
defined, and in that section, there were a bunch of links pointing at
vX.Y.Z/git.html. These links _knew_ about this directory layout to have
the current one at the top-level with stale ones in versioned directories.

I am not involved in the git-scm.com site that shows the documentation,
but I am guessing that it keeps an up to date copy of the preformatted
git-htmldocs repository and shows blob contents directly from the tip of
the history. The preformatted documents in git-htmldocs repository are
meant to be installed in machines of the end users, and do not expect that
end users would keep a forest of documents for all versions next to each
other. For that reason, they are not formatted with the links to older
versions.

So if you are asking for a way to access older versions without any effort
on your part, the answer is no, there is no way to do so. At least, not
that I know of.

If you are willing to do some work, you can keep a forest of documentation
pages for older versions yourself, and format the latest one with the
special macro defined to have the links that point to older versions. If
you can host that result somewhere on the net to help others, it would be
even better. I can tell you how to drive asciidoc to enable the links to
older versions if you are volunteering ;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]