[Savannah-cvs] [Git] (edit) clean-up

[Beuc]

??changed:
-
- git-core is backported on a regular basis using the procedure in 
infra/git.txt. Keep it up-to-date.
-
- Repositories are in /subsystems/cvs/srv/git/project_name.git for now.
- git+ssh is supported in Savane's sv_membersh (delegates to git-shell).
- The git:// lightweight protocol is also available, check etc/xinetd.d/git.
-------------

git-core is backported on a regular basis using the procedure in infra/git.txt. 
Keep it up-to-date.

Repositories are in /subsystems/cvs/srv/git/project_name.git for now.
git+ssh is supported in Savane's sv_membersh (delegates to git-shell).
The git:// lightweight protocol is also available, check etc/xinetd.d/git.

??changed:
-
- * Sub-repositories
-
-  * We need to decide how to allow multiple repositories, or stick with a 
single one. repo.or.cz seems to use project_name.git and 
project_name/forks.git, which sounds cool.
-
-  * repo.or.cz also implements the concept of "forks": 
http://repo.or.cz/m/regproj.cgi?name=git/ which can be used to save bandwidth.
-
-  * The GNU Lilypond maintainers would also like to get one separate 
repository matching each CVS module.
-
- * Implement repository instanciation in Savane - more generally git support. 
[Basic Git support implemented]
-
- * Repository optimization (packing, pruning) needs to be done at some points, 
probably via hooks. git:// doesn't allow this kind of operations. At 
kernel.org, people usually have shell access and a private/non-shared 
repository, so they don't have this kind of issues. The doc says: "packing 
every 4-5MB of loose objects accumulation may be a good rule of thumb." 
(http://www.kernel.org/pub/software/scm/git/docs/everyday.html#Basic%20Repository)
 [It's now automatically done by git]
-
- * Hooks management, as usual.
-
-  * xyz.git/hooks/update for a simple mail-on-commit
-
-  * CIA: http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#ciabot
-
- * Install gitweb. [DONE]
---------

* Sub-repositories
 * We need to decide how to allow multiple repositories, or stick with a single 
one. repo.or.cz seems to use project_name.git and project_name/forks.git, which 
sounds cool.
 * repo.or.cz also implements the concept of "forks": 
http://repo.or.cz/m/regproj.cgi?name=git/ which can be used to save bandwidth.
* Implement repository instanciation in Savane - more generally git support. 
[Basic Git support implemented]
* Repository optimization (packing, pruning) needs to be done at some points, 
probably via hooks. git:// doesn't allow this kind of operations. At 
kernel.org, people usually have shell access and a private/non-shared 
repository, so they don't have this kind of issues. The doc says: "packing 
every 4-5MB of loose objects accumulation may be a good rule of thumb." 
(http://www.kernel.org/pub/software/scm/git/docs/everyday.html#Basic%20Repository).
 Apparently it's done by git when there's a lot of objects committed at once, 
but it may be necessary to do it manually (``git gc --auto``) from time to time.
* Hooks management, as usual.
 * xyz.git/hooks/update for a simple mail-on-commit
 * CIA: http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#ciabot

??changed:
-
- * http://lists.gnu.org/archive/html/savannah-hackers/2006-05/msg00069.html , 
http://lists.gnu.org/archive/html/savannah-hackers/2006-06/msg00010.html : 
thread about implementing git at Savannah
-
- * http://git.or.cz/gitwiki/InterfacesFrontendsAndToolsWishlist#Savane 
http://git.or.cz/gitwiki/GitProjects : mention Savane there :)
-
------

* http://lists.gnu.org/archive/html/savannah-hackers/2006-05/msg00069.html , 
http://lists.gnu.org/archive/html/savannah-hackers/2006-06/msg00010.html : 
thread about implementing git at Savannah
* http://git.or.cz/gitwiki/InterfacesFrontendsAndToolsWishlist#Savane 
http://git.or.cz/gitwiki/GitProjects : mention Savane there :)
* http://git.or.cz/gitwiki/GitHosting http://git.or.cz/gitwiki/GitProjects : 
mention Savane there :)


--
forwarded from 
https://savannah.gnu.org/maintenance/address@hidden://savannah.gnu.org/maintenance