@@ -22,6 +22,8 @@ git push neworigin MYTOPICBRANCH If you have been working on "master" you'll probably need to branch it to another name before you can push. Once you have it in your new github repo, you can do a fresh git-clone to -get the new codes, and then maybe merge your topic branch into your master, if you like. Once all that is done, you can delete your old "couchdb-example-blog" fork. +get the new codes, and then maybe merge your topic branch into your master, +if you like. Once all that is done, you can delete your old +"couchdb-example-blog" fork. Thanks for the patience. README.txt 5e1d34d8683e6bd757aaeda9e50602c023c7f908 Chris Anderson jchris@grabb.it http://github.com/jchris/couchdb-example-blog/commit/1d64dacef5287fff7cbd6b3b58fde087ba4fb6b1 1d64dacef5287fff7cbd6b3b58fde087ba4fb6b1 2009-01-08T09:43:59-08:00 2009-01-08T09:43:59-08:00 rename notice cleanup e27d3ce13043fb5122965ee626e1fbc59f85bab0 Chris Anderson jchris@grabb.it