{"thread":{"id":"3468","subject":"git-svn and working with tags","startedAt":"2006-02-26T11:38:35Z","lastAt":"2006-02-27T00:07:37Z","messageCount":2,"participants":["Nicolas Vilz 'niv'","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16750","messageId":"4401933B.2070109@iaglans.de","threadId":"3468","inReplyTo":null,"subject":"git-svn and working with tags","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-26T11:38:35Z","receivedAt":"2006-02-26T11:38:35Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Hi guys,\n\nI am about to use a git/svn construct for a project next week to track\nmy work and the work of my co-workers.\n\nReason for this is, that all the others are working on windows-boxes and\nI am the lonesome gunman, who wants to work with git on a linux box\ncontributing the others on svn side.\n\nThere is still a lot of work todo, preparing both backends, git and svn,\nfor serving almost the same content structure.\n\nI think, i can do a little scripting to switch my git-SVN-HEAD to\nanother branch. But how am i intended to export tags to svn?\n\ntags should simply go to /tags/\nbranches go to /branches/\nmaster goes to /trunk\n\nA svn-import should be no problem then. The re-exporting back to one\nbranch or svn_path is described in git-svn howto. but how about tags?\n\ndo i have to consider the tags on svn-side manually?\n\nany ideas/hints?\n\nSincerly\nNicolas\n"},{"id":"16778","messageId":"20060227000737.GA9518@hand.yhbt.net","threadId":"3468","inReplyTo":"4401933B.2070109@iaglans.de","subject":"Re: git-svn and working with tags","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2006-02-27T00:07:37Z","receivedAt":"2006-02-27T00:07:37Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Nicolas Vilz 'niv' wrote:\n> Hi guys,\n> \n> I am about to use a git/svn construct for a project next week to track\n> my work and the work of my co-workers.\n> \n> Reason for this is, that all the others are working on windows-boxes and\n> I am the lonesome gunman, who wants to work with git on a linux box\n> contributing the others on svn side.\n> \n> There is still a lot of work todo, preparing both backends, git and svn,\n> for serving almost the same content structure.\n> \n> I think, i can do a little scripting to switch my git-SVN-HEAD to\n> another branch. But how am i intended to export tags to svn?\n> \n> tags should simply go to /tags/\n> branches go to /branches/\n> master goes to /trunk\n> \n> A svn-import should be no problem then. The re-exporting back to one\n> branch or svn_path is described in git-svn howto. but how about tags?\n> \n> do i have to consider the tags on svn-side manually?\n\nYou'll need to do tags on the svn-side manually. git-svn (by-design)\nhas hardly any notion of SVN tags (they're really just branches\ndesignated as read-only). git-svn also fails to track directory copies\n[1], so using git-svn to track a higher-level directory and performing a\ncopy in git and doing git-svn commit may not work so well.\n\nYou can make something that parses a git commit that was imported in\ngit-svn-HEAD. These imported commits have a 'git-svn-id:' line at the\nend that can be parsed for URL and revision number, so you could make it\nfrontend 'svn cp' pretty easily.\n\n[1]: git-diff-* doesn't notice copied/renamed directories. I'm\nactually very thankful for this as it's very prone to bugs in my\nexperience.\n\n-- \nEric Wong\n"}]}