Re: git repos for testing (was: Re: RFC: migrating to git)
Hello, thanks for this Simon! I've ported my work on the type-naturals feature as a git branch, and everything seems to be working as expected so far. I've put my modified repos at http://code.galois.com/cgi-bin/gitweb (their names all start with the type-naturals prefix). I am sending the link to the repos because this server is running the gitweb interface, in case people wanted to play around with it. -Iavor On Thu, Jan 13, 2011 at 9:40 AM, David Brown haske...@davidb.org wrote: On Thu, Jan 13 2011, Benedict Eastaugh wrote: On 13 January 2011 15:30, Johan Tibell johan.tib...@gmail.com wrote: We should set up a git daemon at some point as it's much more efficient that pulling over HTTP. As of version 1.6.6, Git is much more efficient over HTTP than it used to be. http://progit.org/2010/03/04/smart-http.html You do have to install the git smart-http plugin in the server, or it only uses the dumb HTTP protocol. David ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: git repos for testing (was: Re: RFC: migrating to git)
On Thu, Jan 13, 2011 at 4:03 PM, Simon Marlow marlo...@gmail.com wrote: I've made git mirrors of the current GHC HEAD repos (all of them), so people can try out their workflows with git. Poking around in the different repos works for me and is fast. For example: Find new files in base: $ cd libraries/base $ git status Find the definition and uses of threadWaitRead and skip git metadata $ git grep threadWaitRead See when threadWaitRead was added (and introduced in different files): $ git -SthreadWaitRead log (In 2001, by Simon M). Note that sync-all is not executable, which is why I used perl sync-all rather than ./sync-all. You can chmod it, but the chmod will be seen as a local change by git which will get in the way of future pulls, and you'll need to stash or merge or rebase the change (welcome to git :-). This particular problem is due to darcs (which we are mirroring) does not supporting executable permissions on files. We can just set the executable bit on the file and commit it. We should set up a git daemon at some point as it's much more efficient that pulling over HTTP. Johan ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: git repos for testing (was: Re: RFC: migrating to git)
On 13 January 2011 15:30, Johan Tibell johan.tib...@gmail.com wrote: We should set up a git daemon at some point as it's much more efficient that pulling over HTTP. As of version 1.6.6, Git is much more efficient over HTTP than it used to be. http://progit.org/2010/03/04/smart-http.html In fact, GitHub are now using it as their default transport; they mention it in this blog post. https://github.com/blog/767-recent-services-interruptions Benedict. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: git repos for testing (was: Re: RFC: migrating to git)
On Thu, Jan 13 2011, Benedict Eastaugh wrote: On 13 January 2011 15:30, Johan Tibell johan.tib...@gmail.com wrote: We should set up a git daemon at some point as it's much more efficient that pulling over HTTP. As of version 1.6.6, Git is much more efficient over HTTP than it used to be. http://progit.org/2010/03/04/smart-http.html You do have to install the git smart-http plugin in the server, or it only uses the dumb HTTP protocol. David ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
