From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: Google Summer of Code -- 3 Org projects for our first participation! Date: Tue, 24 Apr 2012 21:00:31 +0200 Message-ID: <87r4vdc5v4.fsf@Rainer.invalid> References: <8762cpad2q.fsf@gnu.org> <87ipgp4fr9.fsf@pank.eu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMkyt-0003bJ-3g for emacs-orgmode@gnu.org; Tue, 24 Apr 2012 15:01:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SMkym-0000h4-MI for emacs-orgmode@gnu.org; Tue, 24 Apr 2012 15:00:54 -0400 Received: from plane.gmane.org ([80.91.229.3]:37488) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SMkym-0000gu-F8 for emacs-orgmode@gnu.org; Tue, 24 Apr 2012 15:00:48 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SMkyj-0003h1-72 for emacs-orgmode@gnu.org; Tue, 24 Apr 2012 21:00:45 +0200 Received: from pd9eb4820.dip.t-dialin.net ([217.235.72.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Apr 2012 21:00:45 +0200 Received: from Stromeko by pd9eb4820.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 24 Apr 2012 21:00:45 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Rasmus writes: >> Emacs-Orgmode Git merge tool for Org Files (Andrew Young) > > Interesting. How would such a driver differentiate between normal git? You can add any number of merge drivers to your git config. A merge driver is supposed to know about the expected content of the file types it gets registered for and be indeed more clever about merging than the standard merge algorithms. In particular it needs to know some syntax rules and the semantics of the elements described by that syntax. Let's say you want a merge driver for Changelogs: the standard merge will always produce merge conflicts if two changes are made independently as both changes start at the same point in the ancestor. A merge driver for these knows that the entries in a changelog (the syntax says how these should look) are independent of each other and should be sorted by date (that's the semantics). So as long as both changes only add to the Changelog, no merge conflict occurs: the two hunks will get applied in the correct succession. HTH, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds