# Pointers to CVS 2 GIT imports and gateways

4 messages from 2005-05-08 to 2005-05-09. Participants: Martin Langhoff, H. Peter Anvin.
Thread: https://gitlist.dev/t/538

## Martin Langhoff, 2005-05-08 23:16

Subject: Pointers to CVS 2 GIT imports and gateways
Message-ID: <46a038f90505081616335c2a61@mail.gmail.com>
URL: https://gitlist.dev/e/46a038f90505081616335c2a61%40mail.gmail.com

```
I am looking into importing a cvs repo HEAD history into git using
cvsps. I read throught the thread where Ingo discussed his import of
the kernel sources, but I couldn't find any pointers to what kind of
shell magic or other associated scripts were used, and google hasn't
helped much either.

How do I feed the patchsets into GIT preserving commit msgs and other metadata?

A related question follows: is anyone running git -> cvs gateways, and how? 

pointers to TFM will be much appreciated ;)

cheers,


martin

```

## H. Peter Anvin, 2005-05-09 04:48

Subject: Re: Pointers to CVS 2 GIT imports and gateways
Message-ID: <427EEB9E.9070701@zytor.com>
URL: https://gitlist.dev/e/427EEB9E.9070701%40zytor.com
In-Reply-To: <46a038f90505081616335c2a61@mail.gmail.com>

```
Martin Langhoff wrote:
> 
> A related question follows: is anyone running git -> cvs gateways, and how? 
> 

What would be the point?  The reason for bkcvs was that bk wasn't 
available to everyone.

	-hpa

```

## Martin Langhoff, 2005-05-09 05:41

Subject: Re: Pointers to CVS 2 GIT imports and gateways
Message-ID: <46a038f905050822413ece89b9@mail.gmail.com>
URL: https://gitlist.dev/e/46a038f905050822413ece89b9%40mail.gmail.com
In-Reply-To: <427EEB9E.9070701@zytor.com>

```
On 5/9/05, H. Peter Anvin <hpa@zytor.com> wrote:
> What would be the point?  The reason for bkcvs was that bk wasn't
> available to everyone.

Ease of transition for other automated tasks, perhaps? I don't know
what bits and pieces of infrastructure hang from the old BK-CVS
changeset distribution infrastructure.

Some projects do count on CVS gateways even if they use smarter SCMs.
This is not just because of licensing issues -- sometimes portability
and preexisting tools trump SCM changes.

regards,


martin

```

## H. Peter Anvin, 2005-05-09 13:30

Subject: Re: Pointers to CVS 2 GIT imports and gateways
Message-ID: <427F6610.4020907@zytor.com>
URL: https://gitlist.dev/e/427F6610.4020907%40zytor.com
In-Reply-To: <46a038f905050822413ece89b9@mail.gmail.com>

```
Martin Langhoff wrote:
> 
> Ease of transition for other automated tasks, perhaps? I don't know
> what bits and pieces of infrastructure hang from the old BK-CVS
> changeset distribution infrastructure.
> 

None.  That was all owned by Bitmover.

	-hpa

```