patch for containers library

[Malcolm Wallace]

>> It hardly seems worthwhile to convert the patch to git format, simply to have it in ghc's private repo.
> 
> It's not GHC's private repo, it's the official, central repo.

And how many compilers does the containers package from the git repo currently build with? :-)

> nhc could either check it out from git, set up a darcs mirror of it
> (like ghc does for those libraries that remained in darcs), or use
> tarballs from hackage.

I have had sufficiently painful experiences with git that I do not willingly use it in my spare-time projects, if there is an alternative.

A two-way git/darcs mirror sounds ideal.  nhc98 would need both to be able to pull new developments from the central repo, and to push build-fixes back to it.  Is there any likelihood that one could be set up?  I do not have sufficient git-fu to be confident of doing it myself.

Tarballs seem unlikely to be a solution, since there is no obvious way to contribute back build-fixes.  Unless the maintainers would accept plain old diff patches and roll a new tarball?  Or, and I know this is asking too much, if the maintainers would themselves test patches on more than one compiler...  :-)

Regards,
    Malcolm