Reading group wiki
- Ashok Gautham
- 2014-04-10 @ 19:48
While I really wanted to set up gitit for this group, I have a VPS host
which provides only 512 MB RAM and cabal install causes the disk to
thrash because it uses way more memory for building and linking.
Therefore, I have set up a Github repository for our reading group.
The primary reason behind the repo was the wiki that it allows you to
quickly set up. If you weren't aware of it, the wiki in Github is itself
a git repository.
Therefore, for the wiki https://github.com/ScriptDevil/fprg, there is a
corresponding git repository at
(and for me, email@example.com:scriptdevil/fprg.wiki.git)
However, github is still a bit painful because it does not allow
forking/cloning wikis or sending pull-requests over.
I suggest you do the following
1. Edit online.
I have made the wiki publicly editable
2. git clone https://github.com/ScriptDevil/fprg.wiki.git
Now you should be happily able to pull/fetch and write. However, the
pull-request feature still may not work (I do not know whether setting
upstream would help). In this case, just ping me when you want me to
pull something. I will pull in your changes locally and commit on to the
3. A third option is to have collaborators. I haven't tested this
option. But if you are interested in contributing to the wiki, mail me
your github handle. I will add you as a collaborator.
I have chosen org-mode instead of markdown for the wiki since editing in
Emacs is blissful. However, it shouldn't change much. You are free to
use .md for any notes that you make. Github-wiki seems to choose the
appropriate HTML generator depending on the extension.
Re: [bangalorehaskell] Reading group wiki
- Ashok Gautham
- 2014-04-10 @ 19:54
On Friday 11 April 2014 01:18 AM, Ashok Gautham wrote:
> 2. git clone https://github.com/ScriptDevil/fprg.wiki.git
> Now you should be happily able to pull/fetch and write. However, the
> pull-request feature still may not work (I do not know whether setting
> upstream would help). In this case, just ping me when you want me to
> pull something. I will pull in your changes locally and commit on to the
> central repository.
On further SO-ing, I found
which pretty much echoes point 2.
Looks like this is what people use for managing pulls on wikis. :)