git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Witten <mfwitten@MIT.EDU>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-cvsserver runs hooks/post-receive
Date: Sat, 01 Dec 2007 11:38:37 -0800	[thread overview]
Message-ID: <7vprxq4342.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <BFDB9A00-6E92-4880-9FE7-3D0E392D18A9@mit.edu> (Michael Witten's message of "Sat, 1 Dec 2007 04:17:02 -0500")

Michael Witten <mfwitten@MIT.EDU> writes:

> 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.

      reply	other threads:[~2007-12-01 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  9:12 [PATCH] git-cvsserver runs hooks/post-receive Michael Witten
2007-11-29  0:24 ` Junio C Hamano
2007-11-30  4:06   ` Michael Witten
2007-11-30 12:03     ` Johannes Schindelin
2007-11-30 12:26       ` Michael Witten
2007-11-30 13:19         ` Johannes Schindelin
2007-11-30 13:24         ` Johannes Sixt
2007-12-01  0:19           ` Michael Witten
2007-12-01  2:37     ` Junio C Hamano
2007-12-01  9:17       ` Michael Witten
2007-12-01 19:38         ` Junio C Hamano [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vprxq4342.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mfwitten@MIT.EDU \
    /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).