The newer googlecode pages, such as for BrailleBlaster and liblouisutdml have a number of features that I would like to have. For instance, there is a box that can be checked so that one can use one's Google sign-on password to make a commit, rather than a generated password. These pages also have an updated list of licenses, and Mercurial is the first choice for repository. I need to be able to commit to liblouis. If we keep the old page and just change the repository we may keep the problems as well. It appeard to recognize my username and password but hen have some other sort (and obscure) authentication problem. I need to comit yesterday, or rather several days ago. The files for building liblouis-2.dll and liblouis-2.dll are still not in the repository. We can use the tool for changing from Subversion to Mercurial that Michael mentioned. That will keep the history, but I can't remember when we have used that history. John On Fri, Jun 10, 2011 at 08:23:31AM +1000, James Teh wrote: > Personally, I think losing history is a very bad thing. History makes it > much easier to figure out why a particular change got made and who made > it, etc. Also, is there no way to use the existing project page? If we > move to a new one, we also lose integration with the existing issue > database, downloads, etc. > > Jamie > > On 10/06/2011 8:11 AM, John J. Boyer wrote: > >Michael, > > > >I've been wondering why you were so quiet. > > > >I think the best way to create a Mercurial repository for liblouis would > >be to set up a new googlecode page with a slightly different name, say > >hgliblouis The recent googlecods pages have features that the old ones > >don't. After the repository was set up, I could get a clone of the empty > >repository. I have already created a directory of the liblouis project, > >minus the svn hidden directories. After doing the clone I would just add > >this directory, comit and push. We would lose history, of course, but I > >won't wory about that unless people convince me that it will make a > >difference. Of course, we would then have to link the new page to the > >old one in some way. > > > >John > > > >On Thu, Jun 09, 2011 at 10:38:51PM +0100, Michael Whapples wrote: > >>Personally I would be for that change to mercurial. For your interest, > >>there are tools which can create mercurial repositories from an SVN > >>repository so you do not loose history in the move. Refer to the > >>mercurial website for details on some of them. If you want I could > >>probably do this for you. > >> > >>Michael Whapples > >>On 06/09/11 17:47, John J. Boyer wrote: > >>>Right now I can't commit to the liblouis svn repository. The reason is > >>>stillunder investigation. Both liblouisutdml and BrailleBlaster are on > >>>Mercurial repositories. I have come to like Mercurial better than > >>>Subversion. The move would not be difficult, and the commands are quite > >>>similar. Getting a working copy is simpler, using the clone command. > >>> > >>>What do you think? > >>> > >>>John > >>> > >> > > > > -- > James Teh > Vice President, Developer > NV Access Inc, ABN 61773362390 > Email: jamie@xxxxxxxxxxxx > Web site: http://www.nvaccess.org/ > For a description of the software, to download it and links to > project pages go to http://www.abilitiessoft.com -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities