From: Stefan Karpinski <stefan.karpinski@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andy Parkins <andyparkins@gmail.com>,
Michael Witten <mfwitten@mit.edu>,
git@vger.kernel.org
Subject: Re: [PATCH] git-cvsserver: run post-update hook *after* update.
Date: Thu, 29 Jan 2009 15:26:28 -0800 [thread overview]
Message-ID: <d4bc1a2a0901291526v48e61c1dtde35fa8b77c71560@mail.gmail.com> (raw)
In-Reply-To: <7v3af1enkq.fsf@gitster.siamese.dyndns.org>
On Thu, Jan 29, 2009 at 2:48 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> I think I've seen this one before and I thought it was a sensible thing to
> do (and perhaps I even said so here).
You said it looked sane but that I should resend CCing knowledgable parties.
> Is this a resend? If so, let's queue it in at least 'next' and see if
> anybody screams ;-). For a program near the fringe like cvsserver, not
> many people run it but the small number of people who run it gets hurt
> rather quickly if the updated behaviour breaks their existing practice,
> and sometimes breaking things for them would be the only way to extract
> any response. Yes, it is very unfortunate.
Yes, it is a resend, but I expanded on the commit message, including
my analysis of the potential impact.
next prev parent reply other threads:[~2009-01-29 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1232144521-21947-1-git-send-email-stefan.karpinski@gmail.com>
[not found] ` <1232144521-21947-2-git-send-email-stefan.karpinski@gmail.com>
2009-01-23 5:43 ` [PATCH] git-cvsserver: run post-update hook *after* update Stefan Karpinski
2009-01-23 8:00 ` Junio C Hamano
2009-01-29 21:58 ` Stefan Karpinski
2009-01-29 22:48 ` Junio C Hamano
2009-01-29 23:26 ` Stefan Karpinski [this message]
2009-01-29 22:56 ` Andy Parkins
2009-01-29 21:35 ` [PATCH] git-cvsserver: handle CVS 'noop' command Stefan Karpinski
2009-01-29 22:45 ` Junio C Hamano
2009-01-29 23:39 ` Stefan Karpinski
2009-01-29 23:46 ` Junio C Hamano
2009-01-30 1:12 ` Stefan Karpinski
2009-01-30 1:32 ` Martin Langhoff
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=d4bc1a2a0901291526v48e61c1dtde35fa8b77c71560@mail.gmail.com \
--to=stefan.karpinski@gmail.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).