AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.11.30 15:44 "Re: [Tiff] Switching to gitlab ?", by
2017.11.30 13:52 "Re: [Tiff] Switching to gitlab ?", by Bob Friesenhahn
2017.11.30 14:04 "Re: [Tiff] Switching to gitlab ?", by Even Rouault
2017.11.30 10:31 "Re: [Tiff] Switching to gitlab ?", by Roger Leigh
2017.11.30 13:22 "Re: [Tiff] Switching to gitlab ?", by Olivier Paquet
2017.11.30 14:00 "Re: [Tiff] Switching to gitlab ?", by
2017.11.30 15:26 "Re: [Tiff] Switching to gitlab ?", by Bob Friesenhahn
2017.11.30 15:57 "[Tiff] [DONE] Switching to gitlab !", by Even Rouault
2017.11.30 16:14 "Re: [Tiff] [DONE] Switching to gitlab !", by Even Rouault
2017.11.30 17:36 "Re: [Tiff] [DONE] Switching to gitlab !", by Roger Leigh

2017.11.30 15:44 "Re: [Tiff] Switching to gitlab ?", by

On 2017-11-30 15:26, Bob Friesenhahn wrote:

> On Thu, 30 Nov 2017, Even Rouault wrote:
>
>>> I think that
>>> any future development commits should be to Gitlab. One final commit
>>> should be made to CVS to document that the content there is now
>>> frozen.
>>
>> I was thinking to just decomission the CVS repository (have to find
>> out how to do that exctly),
>> or rename it to some libtiff_historical name. That way, people won't
>> pull from a deprecated
>> repo
>

> The repository itself does contain some other useful historical things > besides libtiff such as a version of libjpeg which supports multiple

> depths in the same build. It would be wrong to just turn off the > server.

We could do git conversions for them as well, and stick them in a "historical" section in gitlab if you like. This would preserve the full history.

If you would like this doing, could you give me a list of CVS modules which need converting? I can't checkout the full set because not all the modules on the CVS server are public, so the checkout fails.

Regards,
Roger