[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [OT] Conflict, an open source project

From: Charles Acknin <charlesacknin_at_gmail.com>
Date: 2007-08-02 11:30:18 CEST

Hey Dennis,

On 8/2/07, Dennis Byrne <dennisbyrne@apache.org> wrote:
> Hello svn devs,
>
> I've started an open source project designed to notify svn users of
> conflicts as they occur, rather than at commit time. It works like this.
> The Conflict client will publish the output from "svn diff" to the Conflict
> server. The Conflict server keeps track of which developer is working with
> which resource. When a conflict is detected, the server puts this in the
> response. The Conflict client then displays this to the developer (IDE
> window, Windows tray icon, etc.).
>
> Have any of you heard of anything like this before? Am told perforce does
> something similar.

I've never had a chance to work on perforce, but I'm skeptical toward
*when* the Conflict client would query or publish data to the Conflict
server. Do you manually have to query the server to receive those
updates? Or is it set as an option when running another command like
"svn/cvs update"? When do you send your updates to the server in
turn?

> One question, is the svn diff output *identical* to cvs diff output? If so,
> Conflict could be used with both.

I can't guaranty it is 100% identical, but I'm sure there are lots of
folks on this list who have this answer. However, svn diff is using
Unidiff and so is cvs.

> Feedback welcome. Let me know if you think svn users would find this useful,
> or if you think it's a POS.

I'm just wondering how different is it from using lock-mechanism if
not granularity? (lock is dealing with paths, or files, Conflict with
lines? bytes?)

Cheers,
Charles

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 2 11:28:48 2007

This is an archived mail posted to the Subversion Dev mailing list.