gitblit.git - Pure java git solution: https://github.com/gitblit-org/gitblit

	Commit message (Collapse)	Author	Age	Files	Lines
*	Reorganized to Apache Standard Directory Layout & integrated Moxie	James Moger	2013-03-27	1	-229/+0
\| \| \| \| \| \| \| \| \|	This is a massive commit which reorganizes the entire project structure (although it is still monolithic), removes the Build classes, and switches to Moxie, a smarter Ant build tookit based on the original Gitblit Build classes. The Ant build script will likely require additional fine-tuning, but this is big step forward.
*	Merged multiple owners (pull request #63)	James Moger	2013-01-23	1	-6/+14
\|\
\| *	Revised multiple owners contribution	James Moger	2013-01-23	1	-93/+61
\| \|
\| *	Merge multiple owners feature (pull request #63, #66)	SHaselbauer	2013-01-21	1	-53/+93
\| \|
* \|	Show indicators for Sparkleshared repositories	James Moger	2013-01-11	1	-0/+6
\|/
*	Fix anonymous browsing of user profile page	James Moger	2012-10-03	1	-1/+4
\|
*	Moved the fork mechanism from a javascript link to a separate page	James Moger	2012-10-02	1	-2/+0
\|
*	Fixed delete repository from repository panel	James Moger	2012-10-01	1	-1/+7
\|
*	Show display name for owner, when possible	James Moger	2012-10-01	1	-8/+17
\|
*	Preliminary implementation of server-side forking (issue 137)	James Moger	2012-09-29	1	-0/+199
	The fork mechanism clones the repository , access restrictions, and other config options. The app has been updated throughout to handle personal repositories and to properly display origin/fork links. In order to fork a repository the user account must have the #fork role, the origin repository must permit forking, and the user account must have standard clone permissions to the repository. Because forking introduces a new user role no existing user accounts can automatically begin forking a repository. This is both a pro and a con. Since the fork has the same access restrictions as the origin repository, those who can access the origin may also access the fork. This is intentional to facilitate integration-manager workflow. The fork owner does have the power to completely change the access restrictions of his/her fork.