From: Michael Witten <mfwitten@MIT.EDU>
To: git@vger.kernel.org
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] git-cvsserver runs hooks/post-receive
Date: Fri, 30 Nov 2007 19:19:32 -0500 [thread overview]
Message-ID: <AB064BA5-1F99-4CCF-9BA5-048BB14E9157@MIT.EDU> (raw)
In-Reply-To: <47500F0B.10300@viscovery.net>
On 30 Nov 2007, at 8:24:27 AM, Johannes Sixt wrote:
>> The difference is that it puts objects in place
>> by hand, requiring the code to mirror hook calls
>> anyway.
>> I'm simply proposing that the code be reworked,
>> so that cvs commits actually become git pushes,
>> so that all future changes to the pushing mechanism
>> are automatically handled.
>
> But in order push something, you must first have the commit in a
> repository. How would git-cvsserver do that? For example, by
> putting objects in place by hand. You gain nothing, except that it
> would push instead of call the hooks directly.
"The difference is that it puts objects in place
by hand, requiring the code to mirror hook calls
anyway."
As far as I can tell, hook calls are the only thing.
However, I still had to write a patch to include post-receive;
by doing everything by hand, git-cvsserver is inherently unsafe
and incomplete over time.
The question is not the RESULT, but HOW YOU GET that result;
the current design is---essentially---a hack; it is written
in perl, after all ;-P
next prev parent reply other threads:[~2007-12-01 0:20 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 [this message]
2007-12-01 2:37 ` Junio C Hamano
2007-12-01 9:17 ` Michael Witten
2007-12-01 19:38 ` 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=AB064BA5-1F99-4CCF-9BA5-048BB14E9157@MIT.EDU \
--to=mfwitten@mit.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).