Git

So I just had the issue, that I encountered a long running local tracking git repo to be huge. And it wasn’t that there are huge (lfs) files stored in it. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 # du -h --max-depth=1 --exclude=.git /var/www/pma.heimdaheim.de/www/ 60K /var/www/pma.heimdaheim.de/www/.github 676K /var/www/pma.heimdaheim.de/www/doc 20K /var/www/pma.heimdaheim.de/www/examples 9.0M /var/www/pma.heimdaheim.de/www/js 5.8M /var/www/pma.heimdaheim.de/www/libraries 59M /var/www/pma.heimdaheim.de/www/po 92K /var/www/pma.heimdaheim.de/www/scripts 28K /var/www/pma.heimdaheim.de/www/setup 28K /var/www/pma.heimdaheim.de/www/sql 1.5M /var/www/pma.heimdaheim.de/www/templates 3.3M /var/www/pma.heimdaheim.de/www/test 9.0M /var/www/pma.heimdaheim.de/www/themes 20M /var/www/pma.heimdaheim.de/www/vendor 92M /var/www/pma.heimdaheim.de/www/node_modules 28K /var/www/pma.heimdaheim.de/www/tmp 200M /var/www/pma.heimdaheim.de/www/ Now after looking at that, we can take a closer look into the git-directory itself (as to what is consuming the space): ...

Well, just like everybody else, I’ve been using phpMyAdmin to do my casual MySQL fixing/work on this website. However, recently the phpMyAdmin developers switched to Git on SourceForge and then to GitHub shortly after that. So, the guy over at Network Jack wrote down what I had already been doing: 1 2 3 git clone --depth=1 git://phpmyadmin.git.sf.net/gitroot/phpmyadmin/phpmyadmin cd phpmyadmin git checkout --track -b PMASTABLE origin/STABLE However, as I said before, they switched from SourceForge to GitHub, thus you need another URL. ...

OK, as Stephen recently asked why there is a double inclusion of in kernel/sysctl.c (and I asked Greg and Randy); I finally decided to write a patch to the LKML for possible inclusion. But, git ain’t easy for people like me (who are used to the easiness of say - subversion or even cvs). So here’s what I did (thanks to Fernando for the help earlier today): 1 2 3 4 5 6 7 8 9 $ vim kernel/sysctl.c // change something $ git checkout -b sysctl // create a new branch from your changes, based upon the master repository $ git commit -a -s // commit the changes to your newly created branch $ git format-patch master..sysctl // Enter a subject and then a separate description // and you should have a new file in the current working directory starting like 0001-*.patch Now you should have a mailable patch, ready to be sent upstream that looks like this: ...