This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 5e1d34d8683e6bd757aaeda9e50602c023c7f908
tree 07433474bf2f96ab0d072205aa38b90f80cd176a
parent cf7ef220ff084d89cec23da3d58b608f018cccec
tree 07433474bf2f96ab0d072205aa38b90f80cd176a
parent cf7ef220ff084d89cec23da3d58b608f018cccec
| name | age | message | |
|---|---|---|---|
| |
README.txt |
README.txt
This project has been renamed. Sorry "couchdb-example-blog" doesn't exactly roll off the tongue. *Welcome to Sofa!* The new project lives at: http://github.com/jchris/sofa/tree/master If you have branches based on this repo, you can get back in sync with my repo in a couple of simple steps: First, "fork" the new Sofa repo on github, then in your newly old "couchdb-example-blog" checkout, run this command: git remote add neworigin git@github.com:THISISYOU/sofa.git And to get your work into the new repo, run (from your old "example blog" local repo): 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. Thanks for the patience.








