Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-18 Thread Mark Rotteveel
On 18-12-2016 10:41, Lester Caine wrote: > CVS still has a number of plus features that github deliberately > destroyed in order to make supporting CODE a priority. Git != GitHub. > When PHP project > was looking to move - yet again - Hg get the vote for a system that > worked better, but the

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-18 Thread Mark Rotteveel
On 18-12-2016 03:24, Helen Borrie wrote: > >> On 18/12/2016 11:48:34 AM, Paul Vinkenoog wrote: >> >> Mark Rotteveel wrote: >> >> > Isn't it time to consider migrating the documentation repository from >> > SourceForge CVS to GitHub? >> > >> > SourceForge itself considers CVS

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-18 Thread Mark Rotteveel
On 17-12-2016 23:46, Paul Vinkenoog wrote: > Mark Rotteveel wrote: > >> Isn't it time to consider migrating the documentation repository from >> SourceForge CVS to GitHub? >> >> SourceForge itself considers CVS deprecated, and having the repository >> on GitHub might increase visibility and will

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-18 Thread Lester Caine
On 18/12/16 02:24, Helen Borrie wrote: >> Mark Rotteveel wrote: >> >> > Isn't it time to consider migrating the documentation repository from >> > SourceForge CVS to GitHub? >> > >> > SourceForge itself considers CVS deprecated, and having the repository >> > on GitHub might increase visibility