From: Jakub Narebski <jnareb@gmail.com>
To: kernel-hacker@bennee.com
Cc: git@vger.kernel.org
Subject: Re: Getting CVS and Git to play nicely in the same box
Date: Thu, 30 Nov 2006 15:16:21 +0100 [thread overview]
Message-ID: <200611301516.22382.jnareb@gmail.com> (raw)
In-Reply-To: <1164894847.21950.98.camel@okra.transitives.com>
Alex Bennee wrote:
> On Thu, 2006-11-30 at 14:08 +0100, Jakub Narebski wrote:
>> Alex Bennee wrote:
>>
>>> Has anyone successfully set up such a working environment? Can anyone
>>> offer any tips on how to make it all work nicely?
>>
>> Why not use git-cvsserver? Or port git-svn to CVS (or use Tailor)?
>
> I can't use git-cvsserver because the main repository is going to have
> to stay on CVS for the time being. I don't think it could be used as a
> drop in replacement for our existing server anyway as it doesn't support
> tagging or branching.
>
> Using git is my own personal indulgence (At least until I can
> demonstrate it's worth while the other migrating ;-).
Perhaps if not git-cvsserver, then git-cvsimport (or parsecvs, or cvs2git)
and git-exportcommit would be what you want.
> It looks like git-svn is the sort of tool I'd want for CVS although I'm
> not sure how it would live with our CVS branched development model. I'll
> have a poke around Tailor and see if that offers any help.
Well, Tailor used to work only with linear histories. But it is meant to
maintain parallel repositories in different formats.
--
Jakub Narebski
next prev parent reply other threads:[~2006-11-30 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 12:39 Getting CVS and Git to play nicely in the same box Alex Bennee
2006-11-30 13:08 ` Jakub Narebski
2006-11-30 13:54 ` Alex Bennee
2006-11-30 14:16 ` Jakub Narebski [this message]
2006-11-30 22:21 ` Robin Rosenberg
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=200611301516.22382.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.