On Fri, 20 Mar 2009, Johannes Schindelin wrote:
On Thu, 19 Mar 2009, david@xxxxxxx wrote:
I see good support for XML being a superset of what's needed to support
ODF or SVG, not a subset.
No, not at all. If we can get away with the default 3-way merge of Git,
the generic XML merge driver be damned.
I would agree, but unless you don't do any auto-merging and punt
everything to the 'conflict resolution tool' the existing merge drivers
won't work for a structured file. And if you do want to do that, it's not
a git project, it's a project for whatever tool you are working from to be
the GUI plus (possibly) a smidge of scripting to call that tool from git.
I'd rather have more file types supported that are useful for the average
user, than a generic XML merge driver that is useful to only a handful of
people.
we are both after the same thing, the most use to the average user.
you look at SVG, ODF word, ODF spreadsheet, OOXML, etc as completely
seperate things that should have support developed seperatly.
I look at the same formats and am seeing a strong similarity between them.
that being that they are all structured XML. so if you get the ability to
handle XML in a configurable way (and define the appropriate
configurations), you not only get the tools for these things, but many
others as well.
I would be a little disappointed if the result of the summer only handled
XML files (and more so if it only handled a handful of popular XML-based
files). I think that there are a number of file types that aren't handled
well by the current merge drivers. Saurabh has voiced the opinion that
many of these have similar problems as the XML situations, so it may end
up making sense to handle them in the same driver.
it would probably be a good thing to see suggestions from a bunch of
people as to what file types they see being useful.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
