2012.12.19 22:02 "Re: [Tiff] CVS server unreachable?", by Frank Warmerdam

Folks,

Despite non-trivial dislike for git, I would not be adverse to migrating libtiff to github for ease of collaboration. I imagine we would be able to preserve the CVS history, but I imagine we would start the bug database over again with the old bugzilla left around in read-only mode.

I hated mercurial when I once used it, and it has limited mind share so I'm hesitant to aim for it.

Best regards,
Frank

On Wed, Dec 19, 2012 at 11:50 AM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:

What I wanted to say, however, is that there really is a need for a backup. There are plenty of ways to accomplish that. Losing the repository history would be very sad.

There is almost certainly a backup but it is done by the same organization. The organization has been highly reliable over the years but it would be useful to have independent backups as well (e.g. via rsync) in case something bad happens to the organization.

An additional value offered by Hg or Git is that organizations can manage their private changes to libtiff using the same tool. It would not be necessary to copy libtiff files into some other version control system in order to version control local changes to libtiff.

--
---------------------------------------+--------------------------------------

I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com

light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | Geospatial Software Developer