From: Martin Langhoff <martin@catalyst.net.nz>
To: Junio C Hamano <junkio@cox.net>
Cc: Andy Parkins <andyparkins@gmail.com>,
Martyn Smith <martyn@catalyst.net.nz>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] Have git-cvsserver call hooks/update before really altering the ref
Date: Tue, 20 Feb 2007 09:59:28 +1300 [thread overview]
Message-ID: <45DA0FB0.8030403@catalyst.net.nz> (raw)
In-Reply-To: <7vfy99t761.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I suspect Martin and Martyn chose 1 to match EPERM (I am looking
> at /usr/include/asm-generic/errno-base.h), and I think your new
> error case falls into EPERM category as well. Since your patch
> is currently queued in 'pu', I can just go ahead and fix it
> myself with "git commit --amend", but an Ack from down under
> would certainly be appreciated ;-).
ACK -- we were either smart in using EPERM or, more likely, super smart
in forcing an error against a real CVS server and watching what it did.
It's better than saying "I don't remember" in any case.
(Sorry about the delay, justback from holidays)
cheers
m
--
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224 UK: 0845 868 5733 ext 7224 MOB: +64(21)364-017
Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------
prev parent reply other threads:[~2007-02-19 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 15:12 [PATCH/RFC] Have git-cvsserver call hooks/update before really altering the ref Andy Parkins
2007-02-13 17:43 ` Junio C Hamano
2007-02-13 17:54 ` Nicolas Pitre
2007-02-13 18:07 ` Junio C Hamano
2007-02-13 18:14 ` Andy Parkins
2007-02-14 5:36 ` Junio C Hamano
2007-02-14 9:13 ` Andy Parkins
2007-02-14 9:33 ` Junio C Hamano
2007-02-19 20:59 ` Martin Langhoff [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=45DA0FB0.8030403@catalyst.net.nz \
--to=martin@catalyst.net.nz \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=martyn@catalyst.net.nz \
/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).