{"thread":{"id":"12000","subject":"[Feature Request] Better Subversion integration","startedAt":"2008-02-10T02:44:59Z","lastAt":"2008-02-15T22:38:17Z","messageCount":10,"participants":["Sam Granieri Jr","Björn Steinbrink","Michael Haggerty","Sebastian Harl","Jan Hudec"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"68153","messageId":"FC5B6F22-27A9-4F0F-85EE-0B72B94C69E2@gmail.com","threadId":"12000","inReplyTo":null,"subject":"[Feature Request] Better Subversion integration","fromName":"Sam Granieri Jr","fromEmail":"sjgdev@gmail.com","sentAt":"2008-02-10T02:44:59Z","receivedAt":"2008-02-10T02:44:59Z","isPatch":false,"sender":{"key":"sjgdev@gmail.com","avatar":null},"body":"Right now, git-svn import (or clone) will convert tags and branches as  \nremote branches.\nI would like it if git could pick up subversion tags and translate  \nthem as git tags upon importing\n\nI also have some concerns with git-svn dcommit\n\nWould it be possible for git-svn dcommit to convert locally created  \ngit tags to subversion tags? How about branches?\n\nOr is git-svn dcommit only meant to push the current working  (git )  \nbranch to whatever (svn) branch you checked out from?\n\nI've been using git since december and I'm trying to convert everyone  \nI know to it from subversion. Unfortunately, I need to use subversion  \nat work. Gits a great tool and I intend to be using it for a while.\n\nSam\n"},{"id":"68162","messageId":"20080210035611.GA2454@atjola.homenet","threadId":"12000","inReplyTo":"FC5B6F22-27A9-4F0F-85EE-0B72B94C69E2@gmail.com","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Björn Steinbrink","fromEmail":"b.steinbrink@gmx.de","sentAt":"2008-02-10T03:56:11Z","receivedAt":"2008-02-10T03:56:11Z","isPatch":false,"sender":{"key":"b.steinbrink@gmx.de","avatar":"https://avatars.githubusercontent.com/u/230962?v=4"},"body":"On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n> Right now, git-svn import (or clone) will convert tags and branches as  \n> remote branches.\n> I would like it if git could pick up subversion tags and translate them \n> as git tags upon importing\n\nSVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\nwhich you can modify at will. Yeah, I know, you _should_ not commit any\nchanges to SVN \"tags\", but shit happens. And once you modify the \"tag\"\nin SVN, you would have to invalidate the git tag, and finding a commit\nthat matches the SVN state of things is probably way too expensive to be\npractical. Maybe some --we-never-mess-up-svn-tag-alike-branches could\nbe added to allow git-svn to create teal git tags though? Dunno, I don't\ncare much. Shouldn't be too hard to find some shell magic to create\ntags, if one wants them.\n\n> I also have some concerns with git-svn dcommit\n>\n> Would it be possible for git-svn dcommit to convert locally created git \n> tags to subversion tags? How about branches?\n\nDidn't need to convert tags yet, but I have a small shell script that\ndoes branching for me (see below). What it does, is to simply look at\nthe history and figure out the first commit that exists in SVN. Then it\ninvokes the svn program and creates a branch in SVN, starting at that\ncommit. Then you can just fetch that branch, rebase your work and commit\naway. Writing a similar hack for tags shouldn't be too hard.\n\nFor example (assuming that you saved the script as git-svn-branch):\ngit checkout -b my_branch remotes/trunk\n// work work work\n.oO( Hm, maybe I should put that into a SVN branch for foobar reason )\ngit-svn-branch my_branch\ngit svn fetch\ngit rebase --onto remotes/my_branch remotes/trunk my_branch\ngit svn dcommit -n # This should now (pretend to) dcommit to my_branch\n\nOne thing it gets wrong (probably, never tried) is that it will take the\nwrong starting point when you cherry-picked a commit from another SVN\nbranch and didn't remove the git-svn-id line. That is because it doesn't\nmake use of the .rev_map files and thus cannot figure out if the\ngit-svn-id line is actually valid.\n\nIIRC git-svn should handle such cherry-picks gracefully, so\nintegrating that thing with git-svn would have some benefits, but I\ndon't speak any perl. Maybe someone else wants to take the job?\n\nHTH\nBjörn\n\n\n#!/bin/sh\nif test \"$1\" = ''\nthen\n\techo \"Usage: git-svn-branch <branch_name>\"\n\texit 127\nfi\n\nCURRENT=$(git rev-list --first-parent --pretty=format:%b HEAD | grep -m1 -o 'git-svn-id: [^ ]*' | sed -e 's/git-svn-id: //')\n\nSRC=${CURRENT%@*}\nREV=${CURRENT#*@}\nURL=$(git config --get svn-remote.svn.url)\n\nURL=$(echo -n \"$URL\" | sed -e 's!//.*@!//!')\nDST=\"$URL/$(git config --get svn-remote.svn.branches | grep -o '^[^:]*' | sed -e \"s/\\*/$1/\")\"\n\nsvn cp -r \"$REV\" \"$SRC\" \"$DST\" -m \"Create branch $1\"\n"},{"id":"68232","messageId":"47AF2BBF.1060403@alum.mit.edu","threadId":"12000","inReplyTo":"20080210035611.GA2454@atjola.homenet","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2008-02-10T16:52:15Z","receivedAt":"2008-02-10T16:52:15Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"Björn Steinbrink wrote:\n> On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n>> Right now, git-svn import (or clone) will convert tags and branches as  \n>> remote branches.\n>> I would like it if git could pick up subversion tags and translate them \n>> as git tags upon importing\n> \n> SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n> which you can modify at will. Yeah, I know, you _should_ not commit any\n> changes to SVN \"tags\", but shit happens. And once you modify the \"tag\"\n> in SVN, you would have to invalidate the git tag, and finding a commit\n> that matches the SVN state of things is probably way too expensive to be\n> practical. Maybe some --we-never-mess-up-svn-tag-alike-branches could\n> be added to allow git-svn to create teal git tags though? Dunno, I don't\n> care much. Shouldn't be too hard to find some shell magic to create\n> tags, if one wants them.\n\nBecause of the way an SVN repository is stored, it should be cheap to\nask SVN whether the contents of a tag in the HEAD revision are identical\nto the contents at the time the tag was created.  If there was any\nchange anywhere under the tag directory, then the node of the tag\ndirectory will be different in the two revisions.\n\nFor that matter, you could ask SVN for information about the revisions\nin which the tags/ directory was changed (this is also very cheap), and\nmake sure that none of those changes modified an existing tag.  This\nscan could be done at the beginning of a conversion to determine which\ntags were handled as pure tags (and therefore convertible as git tags)\nand which were not (and therefore require more complicated handling).\n\nMichael\n"},{"id":"68240","messageId":"20080210175351.GA13411@atjola.homenet","threadId":"12000","inReplyTo":"47AF2BBF.1060403@alum.mit.edu","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Björn Steinbrink","fromEmail":"b.steinbrink@gmx.de","sentAt":"2008-02-10T17:53:51Z","receivedAt":"2008-02-10T17:53:51Z","isPatch":false,"sender":{"key":"b.steinbrink@gmx.de","avatar":"https://avatars.githubusercontent.com/u/230962?v=4"},"body":"On 2008.02.10 17:52:15 +0100, Michael Haggerty wrote:\n> Björn Steinbrink wrote:\n> > On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n> >> Right now, git-svn import (or clone) will convert tags and branches as  \n> >> remote branches.\n> >> I would like it if git could pick up subversion tags and translate them \n> >> as git tags upon importing\n> > \n> > SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n> > which you can modify at will. Yeah, I know, you _should_ not commit any\n> > changes to SVN \"tags\", but shit happens. And once you modify the \"tag\"\n> > in SVN, you would have to invalidate the git tag, and finding a commit\n> > that matches the SVN state of things is probably way too expensive to be\n> > practical. Maybe some --we-never-mess-up-svn-tag-alike-branches could\n> > be added to allow git-svn to create teal git tags though? Dunno, I don't\n> > care much. Shouldn't be too hard to find some shell magic to create\n> > tags, if one wants them.\n> \n> Because of the way an SVN repository is stored, it should be cheap to\n> ask SVN whether the contents of a tag in the HEAD revision are identical\n> to the contents at the time the tag was created.  If there was any\n> change anywhere under the tag directory, then the node of the tag\n> directory will be different in the two revisions.\n> \n> For that matter, you could ask SVN for information about the revisions\n> in which the tags/ directory was changed (this is also very cheap), and\n> make sure that none of those changes modified an existing tag.  This\n> scan could be done at the beginning of a conversion to determine which\n> tags were handled as pure tags (and therefore convertible as git tags)\n> and which were not (and therefore require more complicated handling).\n\nYeah, but what if a \"tag\" in SVN is modified after that? Then the git\ntag becomes kinda invalid, and I see no cheap way to figure out if there\nis a commit somewhere that has the same content of the new \"tag\". That's\nwhat I'm talking about.\n\nThe only way I see to handle that is to create a new commit in git and\ntag that. But IMHO that's totally nuts, because the tag doesn't even\npoint to a commit of the \"real\" branch anymore. And you'd either need to\nreplace/remove the old tag or use a naming scheme that includes some\n@rev marker, both of which are just confusing when talking about tags.\n\nBjörn\n"},{"id":"68248","messageId":"47AF5242.9080804@alum.mit.edu","threadId":"12000","inReplyTo":"20080210175351.GA13411@atjola.homenet","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2008-02-10T19:36:34Z","receivedAt":"2008-02-10T19:36:34Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"Björn Steinbrink wrote:\n> On 2008.02.10 17:52:15 +0100, Michael Haggerty wrote:\n>> Björn Steinbrink wrote:\n>>> On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n>>>> Right now, git-svn import (or clone) will convert tags and branches as  \n>>>> remote branches.\n>>>> I would like it if git could pick up subversion tags and translate them \n>>>> as git tags upon importing\n>>> SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n>>> which you can modify at will. Yeah, I know, you _should_ not commit any\n>>> changes to SVN \"tags\", but shit happens. And once you modify the \"tag\"\n>>> in SVN, you would have to invalidate the git tag, and finding a commit\n>>> that matches the SVN state of things is probably way too expensive to be\n>>> practical. Maybe some --we-never-mess-up-svn-tag-alike-branches could\n>>> be added to allow git-svn to create teal git tags though? Dunno, I don't\n>>> care much. Shouldn't be too hard to find some shell magic to create\n>>> tags, if one wants them.\n>> Because of the way an SVN repository is stored, it should be cheap to\n>> ask SVN whether the contents of a tag in the HEAD revision are identical\n>> to the contents at the time the tag was created.  If there was any\n>> change anywhere under the tag directory, then the node of the tag\n>> directory will be different in the two revisions.\n>>\n>> For that matter, you could ask SVN for information about the revisions\n>> in which the tags/ directory was changed (this is also very cheap), and\n>> make sure that none of those changes modified an existing tag.  This\n>> scan could be done at the beginning of a conversion to determine which\n>> tags were handled as pure tags (and therefore convertible as git tags)\n>> and which were not (and therefore require more complicated handling).\n> \n> Yeah, but what if a \"tag\" in SVN is modified after that? Then the git\n> tag becomes kinda invalid, and I see no cheap way to figure out if there\n> is a commit somewhere that has the same content of the new \"tag\". That's\n> what I'm talking about.\n> \n> The only way I see to handle that is to create a new commit in git and\n> tag that. But IMHO that's totally nuts, because the tag doesn't even\n> point to a commit of the \"real\" branch anymore. And you'd either need to\n> replace/remove the old tag or use a naming scheme that includes some\n> @rev marker, both of which are just confusing when talking about tags.\n\nYou're right; when importing incrementally there is no way to know what\npeople will do with a tag after the initial conversion.  I was thinking\nmore of a one-time conversion.\n\nIf a new tag is created cleanly in subversion (that is, a single copy\nfrom a single location, then you can read the SVN source (trunk or\nbranch name + SVN revision number) directly out of SVN.  A persistent\nlook-up table could keep track of the git hashes corresponding to such\nsources.\n\nIf a clean tag is later modified, would it be reasonable to\n\"retroactively\" create a git branch based on the contents of the old\ntag, and modify that?\n\nThe general case is certainly not easy, but some standard, easy cases\ncould probably be covered.\n\nMichael\n"},{"id":"68283","messageId":"20080210221808.GA16615@atjola.homenet","threadId":"12000","inReplyTo":"47AF5242.9080804@alum.mit.edu","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Björn Steinbrink","fromEmail":"b.steinbrink@gmx.de","sentAt":"2008-02-10T22:18:08Z","receivedAt":"2008-02-10T22:18:08Z","isPatch":false,"sender":{"key":"b.steinbrink@gmx.de","avatar":"https://avatars.githubusercontent.com/u/230962?v=4"},"body":"On 2008.02.10 20:36:34 +0100, Michael Haggerty wrote:\n> Björn Steinbrink wrote:\n> > On 2008.02.10 17:52:15 +0100, Michael Haggerty wrote:\n> >> Björn Steinbrink wrote:\n> >>> On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n> >>>> Right now, git-svn import (or clone) will convert tags and branches as  \n> >>>> remote branches.\n> >>>> I would like it if git could pick up subversion tags and translate them \n> >>>> as git tags upon importing\n> >>> SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n> >>> which you can modify at will. Yeah, I know, you _should_ not commit any\n> >>> changes to SVN \"tags\", but shit happens. And once you modify the \"tag\"\n> >>> in SVN, you would have to invalidate the git tag, and finding a commit\n> >>> that matches the SVN state of things is probably way too expensive to be\n> >>> practical. Maybe some --we-never-mess-up-svn-tag-alike-branches could\n> >>> be added to allow git-svn to create teal git tags though? Dunno, I don't\n> >>> care much. Shouldn't be too hard to find some shell magic to create\n> >>> tags, if one wants them.\n> >> Because of the way an SVN repository is stored, it should be cheap to\n> >> ask SVN whether the contents of a tag in the HEAD revision are identical\n> >> to the contents at the time the tag was created.  If there was any\n> >> change anywhere under the tag directory, then the node of the tag\n> >> directory will be different in the two revisions.\n> >>\n> >> For that matter, you could ask SVN for information about the revisions\n> >> in which the tags/ directory was changed (this is also very cheap), and\n> >> make sure that none of those changes modified an existing tag.  This\n> >> scan could be done at the beginning of a conversion to determine which\n> >> tags were handled as pure tags (and therefore convertible as git tags)\n> >> and which were not (and therefore require more complicated handling).\n> > \n> > Yeah, but what if a \"tag\" in SVN is modified after that? Then the git\n> > tag becomes kinda invalid, and I see no cheap way to figure out if there\n> > is a commit somewhere that has the same content of the new \"tag\". That's\n> > what I'm talking about.\n> > \n> > The only way I see to handle that is to create a new commit in git and\n> > tag that. But IMHO that's totally nuts, because the tag doesn't even\n> > point to a commit of the \"real\" branch anymore. And you'd either need to\n> > replace/remove the old tag or use a naming scheme that includes some\n> > @rev marker, both of which are just confusing when talking about tags.\n> \n> You're right; when importing incrementally there is no way to know what\n> people will do with a tag after the initial conversion.  I was thinking\n> more of a one-time conversion.\n> \n> If a new tag is created cleanly in subversion (that is, a single copy\n> from a single location, then you can read the SVN source (trunk or\n> branch name + SVN revision number) directly out of SVN.  A persistent\n> look-up table could keep track of the git hashes corresponding to such\n> sources.\n> \n> If a clean tag is later modified, would it be reasonable to\n> \"retroactively\" create a git branch based on the contents of the old\n> tag, and modify that?\n\nThat's the first option I described (well, I skipped the \"create a\nbranch\" part). But you would get a history like this:\n\nBefore the tag change:\n\n ---A (tag XYZ)\n     \\\n      B---C---D (trunk)\n\nAfter the tag change:\n\n ---A---A' (tag XYZ)\n     \\\n      B---C---D (trunk)\n\nSo not only does the tag move, but it's also no longer in the history of\ntrunk. And that makes it IMHO a bit confusing/useless to do that. With\nthe branches, you at least _know_ that things can change. Tags are not\nsupposed to do so.\n\nThat said, I'd not oppose any optional support to create such tags, I'd\njust never use it.\n\nBjörn\n"},{"id":"68344","messageId":"20080211084704.GB20741@albany.tokkee.org","threadId":"12000","inReplyTo":"20080210035611.GA2454@atjola.homenet","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Sebastian Harl","fromEmail":"sh@tokkee.org","sentAt":"2008-02-11T08:47:04Z","receivedAt":"2008-02-11T08:47:04Z","isPatch":false,"sender":{"key":"sh@tokkee.org","avatar":"https://gravatar.com/avatar/c19b9c37bd63e5d1dabe8d222904921fb807d53d1d8d41af758a16c066eeb59c?d=mp&s=160"},"body":"Hi,\n\nOn Sun, Feb 10, 2008 at 04:56:11AM +0100, Björn Steinbrink wrote:\n> On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n> > Right now, git-svn import (or clone) will convert tags and branches as  \n> > remote branches.\n> > I would like it if git could pick up subversion tags and translate them \n> > as git tags upon importing\n> \n> SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n> which you can modify at will.\n\nWell, a SVN tag could be represented as a Git branch _and_ a Git tag\npointing to the head of that branch. Whenever any such \"tag branch\"\nadvances, the user should be notified, the user responsible for the\nfurther commits to the SVN \"tag\" should be seriously hurt and the Git\ntag should be overwritten (git tag -f).\n\nSam, is that basically what you want?\n\nCheers,\nSebastian\n\n-- \nSebastian \"tokkee\" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/\n\nThose who would give up Essential Liberty to purchase a little Temporary\nSafety, deserve neither Liberty nor Safety.         -- Benjamin Franklin\n\n"},{"id":"68410","messageId":"E947A49F-4A4C-43F5-8E22-FFAF008E0B82@gmail.com","threadId":"12000","inReplyTo":"20080211084704.GB20741@albany.tokkee.org","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Sam Granieri Jr","fromEmail":"sjgdev@gmail.com","sentAt":"2008-02-11T16:55:37Z","receivedAt":"2008-02-11T16:55:37Z","isPatch":false,"sender":{"key":"sjgdev@gmail.com","avatar":null},"body":"Sebastian,\nI think you have the right idea.\nOne last question\nIf a person wants to work on a tag branch, would the right idea be to  \ncreate new branch on it as to not screw up the previous tag?\n\nOn Feb 11, 2008, at 2:47 AM, Sebastian Harl wrote:\n\n> Hi,\n>\n> On Sun, Feb 10, 2008 at 04:56:11AM +0100, Björn Steinbrink wrote:\n>> On 2008.02.09 20:44:59 -0600, Sam Granieri Jr wrote:\n>>> Right now, git-svn import (or clone) will convert tags and  \n>>> branches as\n>>> remote branches.\n>>> I would like it if git could pick up subversion tags and translate  \n>>> them\n>>> as git tags upon importing\n>>\n>> SVN tags aren't like git tags. A \"tag\" in SVN is just another  \n>> directory,\n>> which you can modify at will.\n>\n> Well, a SVN tag could be represented as a Git branch _and_ a Git tag\n> pointing to the head of that branch. Whenever any such \"tag branch\"\n> advances, the user should be notified, the user responsible for the\n> further commits to the SVN \"tag\" should be seriously hurt and the Git\n> tag should be overwritten (git tag -f).\n>\n> Sam, is that basically what you want?\n>\n> Cheers,\n> Sebastian\n>\n> -- \n> Sebastian \"tokkee\" Harl +++ GnuPG-ID: 0x8501C7FC +++ http:// \n> tokkee.org/\n>\n> Those who would give up Essential Liberty to purchase a little  \n> Temporary\n> Safety, deserve neither Liberty nor Safety.         -- Benjamin  \n> Franklin\n>\n"},{"id":"68452","messageId":"20080211221157.GF20741@albany.tokkee.org","threadId":"12000","inReplyTo":"E947A49F-4A4C-43F5-8E22-FFAF008E0B82@gmail.com","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Sebastian Harl","fromEmail":"sh@tokkee.org","sentAt":"2008-02-11T22:11:57Z","receivedAt":"2008-02-11T22:11:57Z","isPatch":false,"sender":{"key":"sh@tokkee.org","avatar":"https://gravatar.com/avatar/c19b9c37bd63e5d1dabe8d222904921fb807d53d1d8d41af758a16c066eeb59c?d=mp&s=160"},"body":"Hi Sam,\n\nOn Mon, Feb 11, 2008 at 10:55:37AM -0600, Sam Granieri Jr wrote:\n> If a person wants to work on a tag branch, would the right idea be to  \n> create new branch on it as to not screw up the previous tag?\n\nWhy would you want to do that? A tag is supposed to be something\nimmutable. The only reason for having such a \"tag branch\" in the first\nplace is that this seems to be the best representation of what SVN is\ndoing and there's no better way (yet?) to convert it to something more\nGit-like...\n\nCheers,\nSebastian\n\n-- \nSebastian \"tokkee\" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/\n\nThose who would give up Essential Liberty to purchase a little Temporary\nSafety, deserve neither Liberty nor Safety.         -- Benjamin Franklin\n\n"},{"id":"68849","messageId":"20080215223817.GA13178@efreet.light.src","threadId":"12000","inReplyTo":"20080211084704.GB20741@albany.tokkee.org","subject":"Re: [Feature Request] Better Subversion integration","fromName":"Jan Hudec","fromEmail":"bulb@ucw.cz","sentAt":"2008-02-15T22:38:17Z","receivedAt":"2008-02-15T22:38:17Z","isPatch":false,"sender":{"key":"bulb@ucw.cz","avatar":null},"body":"On Mon, Feb 11, 2008 at 09:47:04 +0100, Sebastian Harl wrote:\n> Hi,\n> \n> On Sun, Feb 10, 2008 at 04:56:11AM +0100, Björn Steinbrink wrote:\n> > SVN tags aren't like git tags. A \"tag\" in SVN is just another directory,\n> > which you can modify at will.\n>\n> Well, a SVN tag could be represented as a Git branch _and_ a Git tag\n> pointing to the head of that branch. Whenever any such \"tag branch\"\n> advances, the user should be notified, the user responsible for the\n> further commits to the SVN \"tag\" should be seriously hurt and the Git\n> tag should be overwritten (git tag -f).\n\nThere's no need to have a Git _branch_ together with the tag -- tag is also\na ref.\n\nFor the rest, the user definitely has to be notified, because git push will\n_not_ push out the updated tag if the previous version of it was already\npushed. So the user will have to deal with that manually.\n\nIf there was to be a support for tags in git-svn, I would actually suggest to\nsimply make the name mapping more flexible and simply say, that branches in\ntags/ should be imported to refs/tags (while the rest going to\nrefs/remotes/svn). You see, subversion tags are not annotated (so they don't\nneed special handling) and git-update-ref will update tags just fine.\n\n-- \n\t\t\t\t\t\t Jan 'Bulb' Hudec <bulb@ucw.cz>\n"}]}