From: Andreas Ericsson <ae@op5.se>
To: Jan Hudec <bulb@ucw.cz>
Cc: Theodore Tso <tytso@mit.edu>,
Martin Terreni <martin@terrenis.net>,
Mike Ralphson <mike.ralphson@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: GIT and SCC
Date: Mon, 17 Nov 2008 08:05:16 +0100 [thread overview]
Message-ID: <492117AC.6070200@op5.se> (raw)
In-Reply-To: <20081116215134.GA4719@efreet.light.src>
Jan Hudec wrote:
> On Wed, Nov 05, 2008 at 14:38:25 -0500, Theodore Tso wrote:
>> On Wed, Nov 05, 2008 at 09:23:55PM +0200, Martin Terreni wrote:
>>> http://en.wikipedia.org/wiki/SCC_compliant
>>>
>>> It is probably not much, but this is what I could find in a minute. many
>>> VC system have a SCC complaint API (apart of the native). This protocol
>>> was created by M$ is used by many systems so they are not bound to a
>>> specific VC tool.
>> It's a closed-source, undocumented API that you can only get access to
>> by signing a Microsoft NDA. From the WinMerge API:
>>
>> SCC API is closed API (no public documentation available) some
>> IDE's (e.g. Visual Studio) use. There apparently have couple
>> of reverse-engineered free implementations for SCC API. Status
>> of those are unknown.
>>
>> WARNING: Be very sure you are not submitting any code behing
>> NDA for WinMerge. WinMerge is Open Source so it is not legal
>> to do. And what is worse it would prevent anybody reading that
>> code working with SCC (and perhaps also VCS) support.
>>
>
> I don't really know what this interface is about, but:
> - For VS6 and newer, source control plugin can be implemented by creating
> a dll exporting particular set of controls. This is documented in help
> files that come with VS2005 SDK which is freely downloadable from M$ web,
> so I don't think that would be under NDA.
> - For VS2003 and newer (ie. the .NET based versions), plugins can be
> implemented for almost anything, including source control, by creating
> .net assembly exporting classes that implement some particular interfaces.
> These interfaces are documented in the abovementioned SDK, so again no NDA
> needed.
> I actually started writing such plugin some months back, but since I can only
> work on it at $work (don't have Windooze at ~, not to mention VS2005 license
> -- the SDK is free to download, but requires full, non-express, studio) and
> since it does not look like I could get them use Git at $work anytime soon,
> I didn't work on it too much. Still I could share the basic skeleton and
> the knowledge I have if somebody wanted to move that somewhere.
>
I'm interested. Please email me off-list. I'll pass it on to the monodevelop
people and see what happens. Hopefully they can reuse the same interface so
that mono plugins all of a sudden work everywhere.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2008-11-17 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 18:25 GIT and SCC Martin Terreni
2008-11-05 18:25 ` Shawn O. Pearce
2008-11-05 19:11 ` Mike Ralphson
2008-11-05 19:23 ` Martin Terreni
2008-11-05 19:38 ` Theodore Tso
2008-11-16 21:51 ` Jan Hudec
2008-11-17 7:05 ` Andreas Ericsson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492117AC.6070200@op5.se \
--to=ae@op5.se \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=martin@terrenis.net \
--cc=mike.ralphson@gmail.com \
--cc=spearce@spearce.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox