Footnote in Markdown

There are no footnote syntax in markdown. The closer is a link syntax but not footnote.

... [title] ....
[1]: url

So the only trick want to implement footnote is to use superscript to indicate that LOL

⁰ - \u2070
¹ - \u00b9 (alt+0185)
² - \u00b2 (alt+0178)
³ - \u00b3 (alt+0179)
⁴ - \u2074
⁵ - \u2075
⁶ - \u2076
⁷ - \u2077
⁸ - \u2078
⁹ - \u2079

see also


Migrate Archive Google Code SVN to Git


  • git
  • git-svn


$ sudo apt-get install git
$ sudo add-apt-repository ppa:git-core/ppa
$ sudo apt-get update
$ sudo apt-get install git-svn

¹ Ubuntu 14.04

How To

  1. Download svn dump from Google archive.
  2. Create a local svn repo by load the svn dump.
  3. Start svn daemon.
  4. Create authors.txt to map all svn users to git users.
  5. Create a bare git repo.
  6. git svn clone.
  7. Add git remote then push.
  8. Done.
$ wget
$ gunzip repo.svndump.gz
$ svnadmin create /tmp/repo1
$ svnadmin load /tmp/repo1/ < repo.svndump
$ svnadmin --foreground -d

Start a new terminal Window

$ git svn --stdlayout -A authors.txt clone svn://localhost/tmp/repo1/
$ cd repo1
$ git remote add origin https://repo.git
$ git push --set-upstream origin master


Must map all svn users to git users.

user1 = user1 <>
user2 = user2 <>
(no author) = user3 <>


SSRS Field Name Changes

Basically SSRS is in xml format. We can safely modify with text editor if you know what exactly changes you want to change rather than open with Visual Studio. Of course, I’m not recommend here you can always use text editor to make changes to the report and layout, definitely Visual Studio only has all the complete feature.

The thing I try to point out here is if there is a minor field name changes or dimension name changes you can safely to find and replace with normal text editor. I’ve confirmed that by diff two versions which modified using Visual Studio. Basically the only changes is field name change, not other else.


<ID xsi:type="Level">

Change to

<ID xsi:type="Level">

Move git folder to new repo and retains commit history

If you think a specified folder in your existing repo should be park at other repo then this is a good example to show how to do that and also you never lost any commit history.

Let say I have a repoA with a \folderB which will move into a new repoB

cd \repoA
git filter-branch –-subdirectory-filter folderB -- --all
mkdir folderB
mv * folderB
git add .
git commit

cd ..
git clone repoB.git
cd \repoB
git remote add repoA ..\repoA
git pull repoA master
git remote rm repoA
git push

**caution: You need to create a new repo without any commit yet otherwise you’ll get below error.

fatal: refusing to merge unrelated histories


Clone existing git over new Repo

It is good for us to start from something existing or build on top of existing repo if there is any similar to what we’re looking for rather than build from sketch. I know we can easily to download existing source and directly git add . to you brand new repo. But this will lost all commit history from original author. Usually that is good practice also to remain all the commits history from the day 1. By adding new remote then force push basically this can remain all the previous history.

git clone repo.git
git remote add openshift repo2.git
git commit -a -m "message"
git push
git push openshift master --force