erichdongubler / erichdongubler.github.io Goto Github PK

• Fix the language displays to use the appropriate i18n string
• Fix the domain name

https://bugs.archlinux.org/task/38628#comment154085

This could be potentially awesome. Looks like we'd have to jump through some hoops, though.

For instance, to get Polymer, which is a library for Material Design, it looks like we'd want this tutorial's results just to get Polymer installable:

http://www.aymerick.com/2014/07/22/jekyll-github-pages-bower-bootstrap.html

https://github.com/digitalsparky/jekyll-minifier

https://github.com/snaptortoise/jekyll-rss-feeds/blob/master/feed.category.xml

This would be fairly easy to include dynamically for each category on the page. If we could generate the feed pages dynamically that would also be fantastic...

http://ivanz.com/2009/01/15/selective-import-of-svn-branches-into-a-gitgit-svn-repository/

Basic steps

function git_svn_shallow_clone() {
	local repo_url="${1:?error: expected invocation of the form '<command> <repo_url> [<clone_directory> <other options for `git clone`>]'}"
	shift
	local target_dir="${1:-${repo_url##*/}}"
	shift
	local repo_trunk="$repo_url/trunk"
	echo "Making a shallow clone of $repo_trunk into folder $target_dir..."
	local revision="$(svn info "$repo_trunk" | awk '/^Last Changed Rev:/ { print $4 }')"
	echo "  Cloning last changed revision $revision"
	git svn clone --stdlayout -r"$revision:HEAD" "$repo_url" "$target_dir" "$@" && pushd "$target_dir" > /dev/null && git reset --hard && popd > /dev/null
}

# Example: Clone directly into the CWD.
# Note: if your connection fails midway through the cloning, you can pick up from
# where you left off by simply invoking the clone function again. Neat, right?
git_svn_shallow_clone <url> .

# You may need to run this in your cloned folder if you need to resume cloning from
# an interrupted connection.
git checkout master 

More advanced flow: cloning in an existing repo

git svn init --stdlayout "$repo_url"
git svn fetch -r"$revision:HEAD"

Troubleshooting

• I'm not sure why -s hasn't worked for me at some points, but it HAS given different (failing) behavior than --stdlayout in my most recent testing.
• The repo_url MUST be the root of the standard SVN repo layout.
• The revision MUST be part of the history of the repo_url you specify.

For ALL of the issues above, the only indication that something is wrong is that git will check out an empty repository. To start over, you have to rm -r .git.

...what was that about premature optimization?

Right now, we're currently compatible with RSS, but Atom seems to have more of what we want..

http://en.wikipedia.org/wiki/Atom_(standard)

This is located at the top of the automagic emails.