git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-cvsserver runs hooks/post-receive

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 1, 2007, 19:38 UTC
Message-ID
<7vprxq4342.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<BFDB9A00-6E92-4880-9FE7-3D0E392D18A9@mit.edu>
Michael Witten <mfwitten@MIT.EDU> writes:
Show 10 quoted lines
> On 30 Nov 2007, at 9:37:01 PM, Junio C Hamano wrote:
>
>> I'll queue your patch, but I think it should be enhanced to support
>> post-update for consistency.
>
> I'll send another patch that includes support for post-update.
>
>> I'll queue your patch,
>
> Will the old patch already be in place?

Although I would encourage total replacement patch for things not in 'next' yet, in this case, I think we both would prefer a separate patch that builds on top of the old patch that teaches the server that it should call post-update as well.

I think it is potentially a sensible thing to do to eventually deprecate and then remove post-update hook (as your first patch that is queued already suggests). I was just saying that 'eventually' is not now. When that time comes, if you have a separate patch to teach post-update, that single patch can be reverted independently from the old patch, which should be less error prone than yanking the support out by hand.

Previous: Michael Witten
Message 11 of 11 in “git-cvsserver runs hooks/post-receive”
  1. git-cvsserver runs hooks/post-receiveMichael Witten, Nov 23, 2007
  2. Junio C HamanoNov 29, 2007
  3. Michael WittenNov 30, 2007
  4. Johannes SchindelinNov 30, 2007
  5. Michael WittenNov 30, 2007
  6. Johannes SchindelinNov 30, 2007
  7. Johannes SixtNov 30, 2007
  8. Michael WittenDec 1, 2007
  9. Junio C HamanoDec 1, 2007
  10. Michael WittenDec 1, 2007
  11. Junio C HamanoDec 1, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.