From: Panagiotis Issaris <takis@lumumba.uhasselt.be>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Problem using GIT CVS-server
Date: Wed, 03 May 2006 13:41:27 +0200 [thread overview]
Message-ID: <445896E7.1070306@lumumba.uhasselt.be> (raw)
In-Reply-To: <46a038f90605030311s4e05de2dr90277f97a3a5c223@mail.gmail.com>
Hi,
Martin Langhoff wrote:
> [...]
> thanks a lot for the feedback! cvsserver has mainly been
> tried/debugged with a few repositories, mainly the moodle.git
> repository that we host, which is an import from a CVS repo.
I didnt even know it existed! :) I was looking for an Eclipse plugin
(anyone heard anything about such a beast after 20060313?), when
I accidently stumbled upon the git-cvsserver manpage, somewhere
on the web.
> [...]
> That warning is harmless, and always there. I did look once at
> implementing gzip compression, but in some cases it implies creating
> extra temp files to calculate the size, so I've opted to leave it for
> some other day.
>
> OTOH, we could declare that we handle it, and never actually send a
> gzipped file ;-) as long as we can handle gzipped content from the
> client.
Not really an issue imho :) I just automatically type -z3 whenever I do
a CVS update :)
BTW, thanks for writing git-cvsserver!
With friendly regards,
Takis
prev parent reply other threads:[~2006-05-03 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 8:11 Problem using GIT CVS-server Panagiotis Issaris
2006-05-03 8:17 ` Andreas Ericsson
2006-05-03 8:26 ` Panagiotis Issaris
2006-05-03 8:44 ` Andreas Ericsson
2006-05-03 10:11 ` Martin Langhoff
2006-05-03 11:11 ` Martin Langhoff
2006-05-03 11:36 ` Panagiotis Issaris
2006-05-03 11:42 ` Martin Langhoff
2006-05-03 12:02 ` Panagiotis Issaris
2006-05-03 19:49 ` Junio C Hamano
2006-05-03 21:12 ` Martin Langhoff
2006-05-03 21:21 ` Junio C Hamano
2006-05-03 11:41 ` Panagiotis Issaris [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=445896E7.1070306@lumumba.uhasselt.be \
--to=takis@lumumba.uhasselt.be \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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).