kallithea Changeset - 3c80eb712a78

Changeset - 3c80eb712a78

Parent rev.

Child rev.

[Not reviewed]

beta

0 2 0

Marcin Kuzminski - 15 years ago 2011-02-11 01:28:21
marcin@python-works.com

uncommented migrate tables, docfix

2 files changed with 7 insertions and 7 deletions:

docs/usage/general.rst

rhodecode/lib/dbmigrate/versions/003_version_1_2_0.py

0 comments (0 inline, 0 general)

docs/usage/general.rst

➞

Show inline comments

@@ @@ -9,25 +9,25 @@ Repository deleting @@
 Currently when admin/owner deletes a repository, RhodeCode does not physically
 delete a repository from filesystem, it renames it in a special way so it's
 not possible to push,clone or access repository. It's worth a notice that,
 even if someone will be given administrative access to RhodeCode and will
 delete a repository You can easy restore such action by restoring `rm__<date>`
 from the repository name, and internal repository storage (.hg/.git)
 Follow current branch in file view
 ++++++++++++++++++++++++++++++++++
 In file view when this checkbox is checked the << and >> arrows will jump
-to changesets withing the same branch currently viewing. So for example
+to changesets within the same branch currently viewing. So for example
 if someone is viewing files at 'beta' branch and marks `follow current branch`
 checkbox the << and >> buttons will only show him revisions for 'beta' branch
 Compare view from changelog
 +++++++++++++++++++++++++++
 Checkboxes in compare view allow users to view combined compare view. You can
 only show the range between the first and last checkbox (no cherry pick).
 Clicking more than one checkbox will activate a link in top saying
 `Show selected changes <from-rev> -> <to-rev>` clicking this will bring
 compare view

rhodecode/lib/dbmigrate/versions/003_version_1_2_0.py

➞

Show inline comments

@@ @@ -13,38 +13,38 @@ from rhodecode.model.meta import Base @@
 from rhodecode.model.db import BaseModel
 log = logging.getLogger(__name__)
 def upgrade(migrate_engine):
     """ Upgrade operations go here.
     Don't create your own engine; bind migrate_engine to your metadata
     """
     #==========================================================================
     # Add table `groups``
     #==========================================================================
 #    from rhodecode.model.db import Group
 #    Group().__table__.create()
     from rhodecode.model.db import Group
     Group().__table__.create()
     #==========================================================================
     # Add table `group_to_perm`
     #==========================================================================
 #    from rhodecode.model.db import GroupToPerm
 #    GroupToPerm().__table__.create()
     from rhodecode.model.db import GroupToPerm
     GroupToPerm().__table__.create()
     #==========================================================================
     # Add table `users_groups`
     #==========================================================================
 #    from rhodecode.model.db import UsersGroup
 #    UsersGroup().__table__.create()
     from rhodecode.model.db import UsersGroup
     UsersGroup().__table__.create()
     #==========================================================================
     # Add table `users_groups_members`
     #==========================================================================
     from rhodecode.model.db import UsersGroupMember
     UsersGroupMember().__table__.create()
     #==========================================================================
     # Add table `users_group_to_perm`
     #==========================================================================
     from rhodecode.model.db import UsersGroupToPerm
     UsersGroupToPerm().__table__.create()

0 comments (0 inline, 0 general)