git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: move RelNotes into a directory of their own
Date: Mon, 6 Sep 2010 21:01:09 -0500	[thread overview]
Message-ID: <20100907020109.GI1182@burratino> (raw)
In-Reply-To: <alpine.LFD.2.00.1009062026330.19366@xanadu.home>

Nicolas Pitre wrote:

> There are 108 of them already.  That's a bit more than one third of
> all the files in the Documentation directory already, and still growing.
> 
> Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
> ---
>  .../{RelNotes-1.5.0.1.txt => RelNotes/1.5.0.1.txt} |    0
>  .../{RelNotes-1.5.0.2.txt => RelNotes/1.5.0.2.txt} |    0
[...]

Junio: Because of

	for th in \
		"$T"/*.html "$T"/*.txt \
		"$T"/howto/*.txt "$T"/howto/*.html \
		"$T"/technical/*.txt "$T"/technical/*.html
	do
		h=`expr "$th" : "$strip_leading"'\(.*\)'`
		case "$h" in
		index.html) continue ;;
		esac
		test -f "$h" && continue
		echo >&2 "# rm -f $th"
		rm -f "$th"
	done

this would invalidate old URLs like

	http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.3.txt

, no?  Is there some easy way to set up the appropriate HTTP 301
responses?

Aside from that, this looks like a very good idea.

  reply	other threads:[~2010-09-07  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  0:29 [PATCH] Documentation: move RelNotes into a directory of their own Nicolas Pitre
2010-09-07  2:01 ` Jonathan Nieder [this message]
2010-09-07  4:42   ` Junio C Hamano
2010-09-10  0:00     ` [PATCH] install-webdoc: keep installed RelNotes-*.txt Junio C Hamano

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=20100907020109.GI1182@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nico@fluxnic.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 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).