Re: [Koha-devel] Re: distributed VCS, some thoughts.

[Ryan Higgins]

Well, I think git is the way to go.
The repo can be initially set up to accept pushes from any number of
developers, but can then be restricted so as to force code audit 
before commits.  With the increased flexibility in maintaining local
code modifications and other features, git gets my vote.

rch

Ryan Higgins  

----LibLime----------------------------------
Providing Open-Source Solutions for Libraries
Migration, Training, Maintenance and Support
Featuring Koha ILS : http://liblime.com/koha
---------------------------------------------


----- "MJ Ray" <address@hidden> wrote:
| "Kyle Hall" <address@hidden> wrote:
| > [...] this means that I have to have my work pc publicly available.
| I
| > assume that git has a certain port it works on. Is that correct?
| 
| The other email gives details about the git server ways, but you can
| mirror your git repository to an http site or whatever you can get
| access to.  Alternatively, there are git commands which bundle your
| changes up into an email.  If you can publish web space or send
| email,
| you can share your changes in some way.  It's at least as possible as
| CVS or SVN.  Maybe more so.
| 
| Hope that helps,
| -- 
| MJ Ray - see/vidu http://mjr.towers.org.uk/email.html
| Webmaster/web developer, statistician, sysadmin, online shop maker,
| developer of koha, debian, gobo, gnustep, various mail and web s/w.
| Workers co-op @ Weston-super-Mare, Somerset http://www.ttllp.co.uk/
| 
| 
| _______________________________________________
| Koha-devel mailing list
| address@hidden
| http://lists.nongnu.org/mailman/listinfo/koha-devel