On 10/19/06, Aaron Bentley <aaron.bentley@xxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Webster wrote: > First I want to say every SCM I know of sucks when it comes to tracking > configurations, simply because they don't record or restore file metadata, > like perms, ownership, and acl. Arch supports that kind of metadata. I believe SVN supports recording arbitrary file properties, so it's just a matter of applying those properties to the tree.
yes svn has arbitrary properties which can be manipulated. They are not really intended for permissions, ownership, and acl. To use the svn properties for this requires adding scm tools. Also svn does not allow files in the same directory to live in multiple repos
> Somethings I like the SCM tools to handle. Personally I would like the
> Collaborative document editing and white boarding are other requirements. > odf and svg are xml file formats. I would like to see an efficient > xml diff as part of the SCM core. Using mime types SCM tools can unzip > files, bundles, and use mime type information to the SCM core xml > diff, plain diff > as required. An XML diff/patch or merge will not handle ODF properly. There's too much extra semantic information.
I have only experiment with xml diffs on odf files.
From my experience xml diffs work fine on svg files.
For more information, please refer to http://www.unibw.de/inf2/OO_VCS/oo_rcs_api.html
> I think it is essential that the SCM core include > previsions for multiple > repo partners. You mean multiple merge sources?
yes, Multiple merge sources is handy for collaborative document editing - 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