Commits

Mike Bayer committed c4cab3c

setup for git

Comments (0)

Files changed (5)

+*.pyc
+build/
+dist/
+docs/build/output/
+*.orig
+alembic.ini
+tox.ini
+.venv
+.egg-info
+.coverage

.hgignore

-syntax:regexp
-^build/
-^docs/build/output
-.pyc$
-.orig$
-.egg-info
-.*,cover
-.un~
-\.coverage
-\.DS_Store
-test.cfg
-^.venv

.hgtags

-17fc08fec5474fe4734b55dab67dfbc56c44339c rel_0_1_0
-ff1071e455519fae7ee377337668f77bf78aa30f rel_0_2_0
-3049dc0931e5f3967d37dc2f12cd95bd74104b0d rel_0_2_1
-563831b44738431b7557f49a607cc7d5a73e1f69 rel_0_2_2
-0955bd5ce1bfb027e2090c2d856552a9b9174168 rel_0_3_0
-6905fecaaf4741ce7f595f29c7a64a4e64596326 rel_0_3_1
-92724dd22e831a9c121fb822d8f2c49d03b69f8a rel_0_3_2
-a02e016e8ee567a2df4c29f77f773012b26c860e rel_0_3_3
-a7fdf2b9d0d342e9467c164dbba3a2042ab9eda1 rel_0_4_0
-5113ddecf6da80a0a0f090b9e052b759a799e4f1 rel_0_4_1

docs/build/changelog.rst

 ==========
 
 .. changelog::
+    :version: 0.4.2
+
+    .. change::
+        :tags: misc
+
+      Source repository has been moved to git.
+
     :version: 0.4.1
     :released: Sat Jan 19 2013
 

docs/build/front.rst

 ================
 
 dogpile.core is hosted on `Bitbucket <http://bitbucket.org>`_ - the lead project page is at https://bitbucket.org/zzzeek/dogpile.core.  Source
-code is tracked here using `Mercurial <http://mercurial.selenic.com/>`_.
+code is tracked here using Git.
+
+.. versionchanged:: 0.4.2 Moved source repository to git.
 
 Releases and project status are available on Pypi at http://pypi.python.org/pypi/dogpile.core.
 
 Community
 =========
 
-dogpile.core is developed by `Mike Bayer <http://techspot.zzzeek.org>`_, and is 
+dogpile.core is developed by `Mike Bayer <http://techspot.zzzeek.org>`_, and is
 loosely associated with the `Pylons Project <http://www.pylonsproject.org/>`_.
 As usage of dogpile.core and dogpile.cache increases, it is anticipated that the Pylons mailing list and IRC channel
 will become the primary channels for support.
 ====
 Bugs and feature enhancements to dogpile.core should be reported on the `Bitbucket
 issue tracker
-<https://bitbucket.org/zzzeek/dogpile/issues?status=new&status=open>`_.  If you're not sure 
+<https://bitbucket.org/zzzeek/dogpile/issues?status=new&status=open>`_.  If you're not sure
 that a particular issue is specific to either dogpile.cache or dogpile.core, posting to the `dogpile.cache issue tracker <https://bitbucket.org/zzzeek/dogpile.cache/issues?status=new&status=open>`_
 is likely the better place to post first, but it's not critical either way.