[MonoDevelop] Patch - Support for Git Initial Commit

[Michael Hutchinson]

On Sat, Jun 19, 2010 at 3:31 AM, Dale Ragan <dale.ragan at sinesignal.com> wrote:
> Here's the official kickoff patch to the 'Support for Git' task.  I wanted
> to go ahead and start learning the types and see what was going to be
> needed to retro the existing version control logic for Git.  Since, it is
> different than how an SVN like system functions.
>
> I then added a new C# library project to main/Main.sln called
> MonoDevelop.VersionControl.Git located under
> main/src/addins/VersionControl.  It is mainly a skeleton right now, but
> the add-in is recognized by MonoDevelop and the VersionControlService sees
> the new Git Version Control System and adds it to it's handlers, but since
> I am throwing a NotImplementedException for the CreateRepositoryInstance
> call.  It will not show up yet in the drop down for selecting a source
> control provider.
>
> I also went ahead and added the new project to the build system.  The
> add-in is disabled by default for now.  To enable, pass --enable-git=yes
> to main/configure.  Once I get further along and it's somewhat ready for
> people to try, I will enable it by default.  Configure will print out if
> it is enabled or not:
<snip>

Okay, that all makes sense.

> I am going to type some features up now to make sure everybody is on the
> same page in how it will function.  I am going to keep in mind Mercurial
> since it is very similar to Git during this process.  Hopefully, that will
> make it trivial to add Mercurial support once Git support is done.  Also,
> since this project will depend on GitSharp, what is the policy on
> including third party libraries?  Does it get checked in with the project
> and referenced that way or do you prefer another way?

Depends. For some libraries we ship copies from source in contrib
(e.g. NRefactory, Cecil), but for others we ship binaries in the
addins (e.g. NUnit, Mono.Debugger.Soft). Debian/Ubuntu packagers hate
binaries, but they're a lot simpler for us to deal with, so I'd
suggest going that route initially.

> I like to commit incrementally, as I complete little areas of a feature.
> Do you want me to keep submitting patches or is there plans to get me
> commit access?  Just asking, because there's going to be a lot of patches.

Usual procedure is for us to review and commit the first 4 or so
patches, then give you commit access. I guess this'll be easier when
we're using git :)

I'll leave the review to Lluis since he's most familiar with the VCS addin.

Thanks!

-- 
Michael Hutchinson
http://mjhutchinson.com