Do read only checks on attach as fork of repo list.
We shouldn't leak repo names here to which we don't
have access

Repository groups: super admin shouldn't have the permission set
when he creates a group. Super admins anyway can edit groups even without
explicit permissions set

added alias configuration option for gists.
Used to generate nice looking urls for gists

Prefix gist storage with rc, and store some metadata info into
gist store repos

Implemented simple gist functionality ref #530.

- creation of public/private gists with given lifetime
- rhodecode-gist CLI for quick gist creation

fixed issue with web-editor that didn't preserve executable bit
after editing files

vcs: fixed issues with calling get_changesets method doesn't
throws EmptyRepositoryError when called on empty repos

api: decouple some parts from api CLI script
- also change how we save config file
- method should be always API method
- now we use --save-config for saving api config

Use repo-scann at latest possible state.

- we can ensure every config/checks were made before that step
- it should fix issues with custom GIT paths

created basic TestClass for tests that does
basic pylons stack init

moved top-level tests to rhodecode/tests/other.

- There are no toplevel tests
- moved proper files to fixtures where they should be in the first place

removed duplicate code that set os.environ['RC_SCM_DATA']
this was done via __inject_extras anyway

diff parser: redefined operations stats for changes

- don't loose info about multiple operations like rename + chmod
- new Binary flag when dealing with binary file operations
- fixed diffs after mercurial 2.6 when GIT binary diffs were fixed
- added more tests for multiple operations

- refactored the way diffprocessor returns data. It's
now easier to extract type of operation on binary files
- diffprocessor doesn't append that information into the diff itself

diff parser: prefer git headers over old unified diff headers

Makes the diff show both rename and chmod info and the diff.

diff parser: more correct detection and reporting of binary git diffs

git mode is not just used for binary diffs.

diff parser: match the header order of hg diff --git patches

The output might look like:

diff --git a/A b/B
old mode 100644
new mode 100755
rename from A
rename to B
--- a/A
+++ b/B

Such files were shown as 'modified binary file chmod 100644 => 100755' without
diff.

Now the chmod and diff will be shown ... but still not the rename.

Correct parsing of headers do require a better parser - one do not just use a
regexp.

diff: don't link to removed files

It is 'D' for removed, not 'removed'.

changelog: encode branch names with

ref: https://secure.rhodecode.org/rhodecode-fork-kiilerix/changeset/e175420889dc0d2f530bde8e094cc314e129d1a6

locking API returns objects instead of string messages.

- it's now possible to easily parse the output of lock functions

fixed broken API tests after excluding default user
from users listing

make user listing have edit button to be consistent
with other admin views

hide listing of default user

- there's no option to edit this user, so listing doesn't make sense
- listing and showing builtin default user is confusing

synced vcs with upstream

- moved subprocessio module to VCS
- many small changes to make embedded vcs as similar to to external lib
- use only absolute imports
- patch vcs config during load pylons env

fix broken handling of adding an htsts.
Modifing response/request was having trouble in some redirect cases

managing users groups enforce permissions checks.
User needs at least a read permissions on usergroup to be able
to assign it somewhere.

UserGroup on UserGroup permissions implementation.
- user group can have another usergroup assigned
- it's impossible to assign usergroup on the same usergroup

Added separate default permission for external_auth account
activation. This flag allows users to define separate option of how
activation of external_accounts should be performed.

create a list out of generator.
Generator gets exausted during later executions, and because it's used several times
it causes errors

emailing: log failing emailing as an error

TODO: The failure should be reported back to the user (or the admins). The
system should not silently not send any emails to the targeted recipients.

Even better: it should inform the user whenever emails was (scheduled to be)
sent - and to whom.

html: move "Submit a bug" to make it more clear that it is for RhodeCode, not the repo

RhodeCode _could_ contain a bug tracker and this link _could_ be for filing
bugs for the hosted projects.

Moving the link to the RhodeCode info makes it more clear that it is for
RhodeCode bugs.

The server instance is however something local, not directly related to the
upstream.

added initial_repo_scan flag for controll if repo scaning should be performed on every startup.
There's always paster repo-scan or repo scann triggered from admin pannel

Unified the paginators for pylons and YUI.
- YUI based paginators now behave more like the ones generated with pylons
- introduced new custom pylons paginator for customizations needed to unify both

invalidation: don't create CacheInvalidation records on startup

Creating the records early gave an advantage before lightweight was introduced.
With lightweight it is no longer necessary.

The records will be created on demand anyway and there is no reason to create and
maintain them before they are used.

invalidation: merge .invalidate and .set_valid as .test_and_set_valid

This simplifies the internal API and avoids leaking CacheInvalidation instances
and cache keys.

removed assertion about ancestor revision.
log this as a warning, and let it proceed.
ref #829

Removed shortlog aka lightweight changelog.
Current version of changelog is fast and condensed.
There's no sense to keep changelog duplicity.

Use changelog controller for displaying history of files.
step 1 for removing obsolete shortlog

api: don't report invalidated cache_keys after invalidating a repo

The keys are an implementation detail and is never relevant outside RhodeCode
internals and should not be leaked.

compare: move get_changesets to compare controller where it is used - 2nd half that was lost in 6c79bfcd3b54

That is a better location than the pull request model. It should probably be
split up and moved to the backend specific Repository classes.