{"thread":{"id":"25111","subject":"svn propset","startedAt":"2010-09-15T18:52:25Z","lastAt":"2010-09-29T08:12:05Z","messageCount":2,"participants":["schachtobi","Andreas Stricker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"150744","messageId":"4C9115E9.4080900@web.de","threadId":"25111","inReplyTo":null,"subject":"svn propset","fromName":"schachtobi","fromEmail":"schachtobi@web.de","sentAt":"2010-09-15T18:52:25Z","receivedAt":"2010-09-15T18:52:25Z","isPatch":false,"sender":{"key":"schachtobi@web.de","avatar":null},"body":"In response to Ramana,\n\nyou talked about the svn:ignore property and suggested to have a special\ncommand to set this property. But I think first it could be done\nautomatically using the semantics git allready has and second there are\nother properties that could be treated the same way:\n\n* svn:mime-type\n* svn:ignore\n* svn:keywords (is there something like this in git?)\n* svn:externals (not yet supported? Found nothing so far)\n  except solutions here:\nhttp://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins\n  but this is not the same since the client has to setup the links,\nrepositories etc. And they do not come automatically as in subversion.\n  I guess submodules is the proper replacement. But still having the\nsvn:externals from a pull this could be done automatically without the\nneed for scripting. And the dcommit should also work for the submodules.\n* svn:bugtraq*\n* svn:mergeinfo\n\nfor me the svn:merginfo and the svn:externals would be most benifitial\nsince our team uses this a lot and without being able to set those from\ngit it will be not possible for me to use git for a svn client to do the\nmerges.\n\nSo are there plans or updates to the problems I have encountered?\n\nThanks!\n\nregards,\nTobias\n"},{"id":"152033","messageId":"4CA2F4D5.6010601@futurelab.ch","threadId":"25111","inReplyTo":"4C9115E9.4080900@web.de","subject":"Re: svn propset - focus on svn:externals","fromName":"Andreas Stricker","fromEmail":"astricker@futurelab.ch","sentAt":"2010-09-29T08:12:05Z","receivedAt":"2010-09-29T08:12:05Z","isPatch":false,"sender":{"key":"astricker@futurelab.ch","avatar":"https://gravatar.com/avatar/007ac93f9abc20ee78c5169783fcf3f065d470d6b53d47050e30cf7ebad5025b?d=mp&s=160"},"body":"schachtobi wrote:\n> * svn:externals (not yet supported? Found nothing so far)\n>   except solutions here:\n>\nhttp://panthersoftware.com/articles/view/3/svn-s-svn-externals-to-git-s-submodule-for-rails-plugins\n>   but this is not the same since the client has to setup the links,\n> repositories etc. And they do not come automatically as in subversion.\n\nThen there is also the git-svn-clone-externals [1]\n\n>   I guess submodules is the proper replacement. But still having the\n> svn:externals from a pull this could be done automatically without the\n> need for scripting. And the dcommit should also work for the submodules.\n\nGit submodules could help here, but I doubt there is a full automated\nsolution that will work in all circumstances. Here at work we have an\nexcessive use of svn:externals that points diagonally through the whole\nrepository.\n\n> for me the svn:merginfo and the svn:externals would be most benifitial\n> since our team uses this a lot and without being able to set those from\n> git it will be not possible for me to use git for a svn client to do the\n> merges.\n\nFor me the support for the new svn:externals syntax [2] would be a first\nhuge step forwards. With the proper support for the new syntax I may use\nthe git-svn-clone-externals [1] to fetch the externals.\n\nI started to extend git-svn to support those new syntax and pushed\nit to github [3] for those who are interested. I'm a bit busy at the\nmoment, but like to continue this work.\n\nRegards, Andy\n\n[1] http://github.com/andrep/git-svn-clone-externals\n[2] http://subversion.apache.org/docs/release-notes/1.5.html#externals\n[3] http://github.com/AndyStricker/git#\n\n\n"}]}