From: Jeff King <peff@peff.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: Aonodensetsu <remok99999@gmail.com>, git@vger.kernel.org
Subject: Re: Pro Git book URL on https://git-scm.com/
Date: Mon, 5 Dec 2022 04:23:40 -0500 [thread overview]
Message-ID: <Y424nPuHH+/susGO@coredump.intra.peff.net> (raw)
In-Reply-To: <d9253ae3-9fc4-f426-a737-792bf158bd4e@web.de>
On Sat, Dec 03, 2022 at 01:02:41PM +0100, René Scharfe wrote:
> Am 03.12.22 um 12:23 schrieb Aonodensetsu:
> > The Git documentation has been moved (probably by accident) to
> > https://git-scm.com/book/pl/v1%20z (notice the %20z at the end). This
> > is a bug and makes all redirections fail with a 500 error, since they
> > try to redirect to the correct address.
>
> I can't find "v1 z" or "v1%20z" neither in the repository for the
> website (https://github.com/git/git-scm.com) nor in the one for the book
> (https://github.com/progit/progit2). So I'm not sure what's going on
> here, but reporting it as an issue via the website repository should get
> the right people to take a look, I assume.
The book content is added to the sql database by a ruby job. But we
stopped running that job for the v1 (first-edition) book at some point
before 2017. I don't have an exact date, but I removed the generation
code in 495fa431 (drop book.rake, 2017-10-08). We later restored it so
that we could re-import historical versions (say, if the database
crashed and was wiped), but it finally went away in f474e35c (Remove
link to 1st book edition, 2018-11-21).
Frankly, I'm surprised there's any v1 content left, since we've had to
re-build the database from scratch a few times over the years.
-Peff
prev parent reply other threads:[~2022-12-05 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 11:23 Aonodensetsu
2022-12-03 12:02 ` Pro Git book URL on https://git-scm.com/ René Scharfe
2022-12-05 9:23 ` Jeff King [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y424nPuHH+/susGO@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=remok99999@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).