git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Petr Baudis <pasky@suse.cz>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Adjust for the new way of enabling the default post-update hook
Date: Mon, 11 Aug 2008 15:57:36 -0700	[thread overview]
Message-ID: <7vfxpbuplr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080811223446.8342.37008.stgit@localhost> (Petr Baudis's message of "Tue, 12 Aug 2008 00:34:46 +0200")

Petr Baudis <pasky@suse.cz> writes:

> The post-update hook, which is required to be enabled in order for
> the repository to be accessible over HTTP, is not enabled by
> chmod a+x anymore, but instead by dropping the .sample suffix.

Thanks for attention to the details.

> This patch emphasizes this change in the release notes (since
> I believe this is rather noticeable backwards-incompatible change).

Anybody who tries to chmod an nonexisting file would notice, so I
personally think you are making a mountain out of a molehill.

Nevertheless, mentioning it in the release notes would be a good finishing
touch.

> +The standard way of making repositories friendly to dumb protocols
> +(i.e. HTTP) changed: instead of making hooks/post-update executable,
> +hooks/post-update.sample is to be moved to hooks/post-update.

I'm actually not very happy with the above wording that makes it sound as
if any of the samples are part of any "standard way".

The only standard thing is to make sure update-server-info runs.  You do
not have to start from the sample hook to do so, even though it may be one
of the easiest ways.

The rest of the patches look good, but have you actually made sure
AsciiDoc markups are correct (I am not complaining, just asking, as I
haven't)?

  reply	other threads:[~2008-08-11 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 22:34 [PATCH] Adjust for the new way of enabling the default post-update hook Petr Baudis
2008-08-11 22:57 ` Junio C Hamano [this message]
2008-08-11 23:05   ` Petr Baudis
2008-08-11 23:15     ` 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=7vfxpbuplr.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).