The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Oct 13, 2009
Git# is a .NET and Mono version of the popular source code management system, Git, obtained by porting JGit to C#. Other related projects are: msysgit and gitextensions.
Git# is meant to be “fully compatible with the original git and shall be a light weight library for cool applications that are based on git as their object database or are reading or manipulating repositories in some way.”
The latest release of Git# is only an Alpha 0.1.3 with the command line interface still under work, but it offers a stable core library that can be used from .NET projects to access Git repositories. The API is still subject to change.
A discussion group is set up for Git# for those interested to participate and to know more about the project. A working demo has been made available online on GitHub. A few examples show how to get started with Git#. The license used for this project is BSD, the same as JGit’s.
msysgit is a Git provider for Windows, a project more mature and complete than Git#, but “it can not be easily extended by or embedded in other applications”, according to Git# authors. The license used is GNU GPL v2.
Yet another related project is gitextensions which offers a number of tools to ease working with Git from Windows. It features integration with Windows Explorer and it has a plug-in for VS 2005/2008. The license is GNU GPL v3.
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
No comments
Watch Thread Reply