From: Michael Witten <mfwitten@MIT.EDU>
To: git@vger.kernel.org
Cc: 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 07:26:41 -0500 [thread overview]
Message-ID: <BDA3CE08-FFA4-4D84-A2FC-5810AAA6EEAB@MIT.EDU> (raw)
In-Reply-To: <Pine.LNX.4.64.0711301202230.27959@racer.site>
On 30 Nov 2007, at 7:03:15 AM, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 29 Nov 2007, Michael Witten wrote:
>
>> In any case, I haven't taken a thorough look at how git-cvsserver
>> works,
>> but it seems to duplicate a lot of git-receive-pack.
>>
>> How about turning git-cvsserver into a true middleman, so that it
>> constructs a 'temporary git working tree' and then does a real git-
>> push
>> into the final git repository.
>
> That would yield a horrible performance.
>
> Would be opposed, if a regular cvsserver user,
How come?
git-cvsserver it seems already does just that!
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.
It just makes sense as far as design; git-cvsserver
should be an adaptor between the two kinds of repositories,
not an infiltrator.
next prev parent reply other threads:[~2007-11-30 12:27 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 [this message]
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
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=BDA3CE08-FFA4-4D84-A2FC-5810AAA6EEAB@MIT.EDU \
--to=mfwitten@mit.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).