{"thread":{"id":"9675","subject":"git-svn tags and branches","startedAt":"2007-08-27T14:08:02Z","lastAt":"2007-08-30T16:01:46Z","messageCount":17,"participants":["Giuseppe Bilotta","David Kastrup","Mike Hommey","Benoit SIGOURE","Andreas Ericsson","Junio C Hamano","Eric Wong","Peter Baumann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"51715","messageId":"faulrb$483$1@sea.gmane.org","threadId":"9675","inReplyTo":null,"subject":"git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-27T14:08:02Z","receivedAt":"2007-08-27T14:08:02Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"Hello all,\n\nI've recently started using git and I like it so much that\nI've decided to start using it also for some svn-based\nprojects (in particular, rbot http://linuxbrit.co.uk/rbot).\n\nThe long term goal would be to move the project to git, but\nfor the time being (among the other things we're waiting for\nTrac to have proper support for git, which is something that\nwon't happen before Trac 0.12 at least) I've decided to\nexperiment with a dual git/svn development process, using\n(of course) git-svn.\n\nMy experience with toying around with it for a couple of\nhours has been extremely positive, but I've got some\nquestions, especially about the tags and branch management.\n\nCurrently, git-svn imports svn tags as lightweight git tags.\nI was susprised when I discovered this (from 'git describe'\nfailing and some helpful assistance on the IRC channel), so\nI'm now wondering: is there a technical reason why they\naren't converted to annotated tags? If not, would it be\npossible to implement this in git-svn, possibly with some\nway to 'fix' existing git-svn repository?\n\nMy second question concerns the uses of branche in git-svn,\nbut it might come from a not perfect understanding of the\nbranching mechanism in git (and yes, I've read the\ndocumentation and Wiki pages).\n\nIf I understand correctly, svn branches are imported in\ngit-svn as remote branches (refs/remote/*) and are\nautomatically updated on git-svn fetch or git-svn fetch-all.\n\nIn my experiments, however, I've noticed the following\nbehaviour.\n\ngit branch --track trunk remote/trunk\n\ngit svn dcommit\n\nNow, master and remote/trunk point to the new roundtripped\nchanges, but the branch 'trunk' (in git) remains pointing to\nthe old remote/trunk head. I would have expected the --track\noption to keep trunk in sync with remote/trunk ...\n\nOr am I missing something obvious?\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51717","messageId":"867inhqaj9.fsf@lola.quinscape.zz","threadId":"9675","inReplyTo":"faulrb$483$1@sea.gmane.org","subject":"Re: git-svn tags and branches","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-08-27T15:09:30Z","receivedAt":"2007-08-27T15:09:30Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Giuseppe Bilotta writes:\n\n> I've recently started using git and I like it so much that\n> I've decided to start using it also for some svn-based\n> projects (in particular, rbot http://linuxbrit.co.uk/rbot).\n>\n> The long term goal would be to move the project to git, but\n> for the time being (among the other things we're waiting for\n> Trac to have proper support for git, which is something that\n> won't happen before Trac 0.12 at least) I've decided to\n> experiment with a dual git/svn development process, using\n> (of course) git-svn.\n>\n> My experience with toying around with it for a couple of\n> hours has been extremely positive, but I've got some\n> questions, especially about the tags and branch management.\n>\n> Currently, git-svn imports svn tags as lightweight git tags.\n\nIt does? I see them as branches.\n\n> I was susprised when I discovered this (from 'git describe'\n> failing and some helpful assistance on the IRC channel), so\n> I'm now wondering: is there a technical reason why they\n> aren't converted to annotated tags? If not, would it be\n> possible to implement this in git-svn, possibly with some\n> way to 'fix' existing git-svn repository?\n\nI actually don't see how one can safely make them tags at all (rather\nthan branches) since Subversion does not enforce the members of a\n\"tags\" subdirectory to remain unchanged after the initial copy.\nBasically, tags are not different from branches in Subversion from\nwhat you can do with them.\n\n> My second question concerns the uses of branche in git-svn,\n> but it might come from a not perfect understanding of the\n> branching mechanism in git (and yes, I've read the\n> documentation and Wiki pages).\n\nI'll leave that question to people who actually understand git-svn and\ngit branches.\n\n-- \nDavid Kastrup\n"},{"id":"51719","messageId":"20070827153138.GA12936@glandium.org","threadId":"9675","inReplyTo":"867inhqaj9.fsf@lola.quinscape.zz","subject":"Re: git-svn tags and branches","fromName":"Mike Hommey","fromEmail":"mh@glandium.org","sentAt":"2007-08-27T15:31:38Z","receivedAt":"2007-08-27T15:31:38Z","isPatch":false,"sender":{"key":"mh@glandium.org","avatar":"https://avatars.githubusercontent.com/u/1038527?v=4"},"body":"On Mon, Aug 27, 2007 at 05:09:30PM +0200, David Kastrup wrote:\n> I actually don't see how one can safely make them tags at all (rather\n> than branches) since Subversion does not enforce the members of a\n> \"tags\" subdirectory to remain unchanged after the initial copy.\n> Basically, tags are not different from branches in Subversion from\n> what you can do with them.\n\nWell, git-svn could make tags when the tag/branch is created in subversion,\nand then create a branch on the first commit on top of that tag/branch in\nsvn.\n\nMike\n"},{"id":"51721","messageId":"A0329662-9C87-44C2-84E4-4F60DCC1E95F@lrde.epita.fr","threadId":"9675","inReplyTo":"20070827153138.GA12936@glandium.org","subject":"Re: git-svn tags and branches","fromName":"Benoit SIGOURE","fromEmail":"tsuna@lrde.epita.fr","sentAt":"2007-08-27T15:36:20Z","receivedAt":"2007-08-27T15:36:20Z","isPatch":false,"sender":{"key":"tsunanet@gmail.com","avatar":"https://avatars.githubusercontent.com/u/128281?v=4"},"body":"On Aug 27, 2007, at 5:31 PM, Mike Hommey wrote:\n\n> On Mon, Aug 27, 2007 at 05:09:30PM +0200, David Kastrup \n> wrote:\n>> I actually don't see how one can safely make them tags at all (rather\n>> than branches) since Subversion does not enforce the members of a\n>> \"tags\" subdirectory to remain unchanged after the initial copy.\n>> Basically, tags are not different from branches in Subversion from\n>> what you can do with them.\n>\n> Well, git-svn could make tags when the tag/branch is created in \n> subversion,\n> and then create a branch on the first commit on top of that tag/ \n> branch in\n> svn.\n>\n\nOr update the tag ref in Git so that it points to the new \"HEAD\" of \nthe SVN tag. But all in all, it's more consistent to have it look \nlike a branch from the Git point of view, because that's really what \nit is after all.\n\n-- \nBenoit Sigoure aka Tsuna\nEPITA Research and Development Laboratory\n\n\n"},{"id":"51722","messageId":"faurcl$p0o$1@sea.gmane.org","threadId":"9675","inReplyTo":"867inhqaj9.fsf@lola.quinscape.zz","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-27T15:42:36Z","receivedAt":"2007-08-27T15:42:36Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On Monday 27 August 2007 17:09, David Kastrup wrote:\n\n> Giuseppe Bilotta writes:\n>>\n>> Currently, git-svn imports svn tags as lightweight git tags.\n> \n> It does? I see them as branches.\n\nOh, I thought that them being in refs/remote/tags meant they\nwere remote tags. But yes, I had noticed them appearing with\ngit branch -r\n\n>> I was susprised when I discovered this (from 'git describe'\n>> failing and some helpful assistance on the IRC channel), so\n>> I'm now wondering: is there a technical reason why they\n>> aren't converted to annotated tags? If not, would it be\n>> possible to implement this in git-svn, possibly with some\n>> way to 'fix' existing git-svn repository?\n> \n> I actually don't see how one can safely make them tags at all (rather\n> than branches) since Subversion does not enforce the members of a\n> \"tags\" subdirectory to remain unchanged after the initial copy.\n> Basically, tags are not different from branches in Subversion from\n> what you can do with them.\n\nAlthough this is technically true, I doubt there are many Subversion\nprojects which alter the members of a tags subdirectory. So the fact\nthat it's technically possible doesn't really mean it happens.\n\nI mean, even in git you can do some pretty dirty tag stuff. It may\nnot be as straightforward as in svn, but still ...\n\nSo yes, I still think that an option to convert svn tags to annotated\ntags would be appropriate. Wether or not it should be default, it's\na different matter, of course.\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51733","messageId":"fav0e9$bbh$1@sea.gmane.org","threadId":"9675","inReplyTo":"A0329662-9C87-44C2-84E4-4F60DCC1E95F@lrde.epita.fr","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-27T17:08:47Z","receivedAt":"2007-08-27T17:08:47Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On Monday 27 August 2007 17:36, Benoit SIGOURE wrote:\n\n> On Aug 27, 2007, at 5:31 PM, Mike Hommey wrote:\n> \n>> On Mon, Aug 27, 2007 at 05:09:30PM +0200, David Kastrup \n>> wrote:\n>>> I actually don't see how one can safely make them tags at all (rather\n>>> than branches) since Subversion does not enforce the members of a\n>>> \"tags\" subdirectory to remain unchanged after the initial copy.\n>>> Basically, tags are not different from branches in Subversion from\n>>> what you can do with them.\n>>\n>> Well, git-svn could make tags when the tag/branch is created in \n>> subversion,\n>> and then create a branch on the first commit on top of that tag/ \n>> branch in\n>> svn.\n> \n> Or update the tag ref in Git so that it points to the new \"HEAD\" of \n> the SVN tag.But all in all, it's more consistent to have it look \n> like a branch from the Git point of view, because that's really what \n> it is after all.\n\nYes and no. By making it just a branch you lose the tag POV on that\nparticular commit, and this is, in a way, a loss of information: yes, it\ncan behave like a branch but most projects use it as a tag.\n\nI think the best approach is to have an annotated tag 'tagname'\ncorresponding to the tags/tagname copy on the svn side in addition\nto the 'tags/tagname' branch that is currently used to track its head.\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51782","messageId":"cb7bb73a0708290141y159d6bbfj2bac23af5e86bb15@mail.gmail.com","threadId":"9675","inReplyTo":"46D4ECE2.9020806@vilain.net","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-29T08:41:07Z","receivedAt":"2007-08-29T08:41:07Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On 8/29/07, Sam Vilain wrote:\n> Giuseppe Bilotta wrote:\n\n> > I gather from the man page that doing this is highly frowned upon, and\n> > requires manual intervention from all the poor souls that pulled in\n> > the mean time.\n>\n> Right, but I think the bad practice should be propagated anyway. It\n> will affect virtually no-one, and serves to make it the case that even\n> if such a thing happened, then just fetching the tag gives the expected\n> behaviour.\n>\n> However I'd be prepared to accept that perhaps new tags should be made,\n> eg \"tags/svntagname.r1234\", to reflect the fact there are there multiple\n> tags with the same name but different contents.\n\nUrgh. I think I like this idea even less. just use the tag 'tagname'\nand move it around then :)\n\nBTW can git have a tag and a branch with the same name? If not, I\nwould recomment the use of 'name' for the tag, 'name-branch' for the\nbranch, and 'tag-name-branch' for the branch under the tag.\n\n> > I've been looking through the git-svn code to see if I could try an\n> > implementation myself, but I must confess that the task seems way over\n> > me ... I can't really wrap my mind around the git-svn code enough to\n> > implement it.\n>\n> Coming up with agreed test cases is half (indeed sometimes most of) the\n> work.\n\nThe only two svn projects I cooperate with don't have this particular\nsituation. IIRC David mentioned the case?\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51783","messageId":"46D534CB.6030406@op5.se","threadId":"9675","inReplyTo":"cb7bb73a0708290141y159d6bbfj2bac23af5e86bb15@mail.gmail.com","subject":"Re: git-svn tags and branches","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-08-29T08:56:43Z","receivedAt":"2007-08-29T08:56:43Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Giuseppe Bilotta wrote:\n> BTW can git have a tag and a branch with the same name?\n\nYes it can. I'm unsure as to what takes precedense.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"51784","messageId":"7v4piisolb.fsf@gitster.siamese.dyndns.org","threadId":"9675","inReplyTo":"cb7bb73a0708290141y159d6bbfj2bac23af5e86bb15@mail.gmail.com","subject":"Re: git-svn tags and branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-08-29T08:59:44Z","receivedAt":"2007-08-29T08:59:44Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Giuseppe Bilotta\" writes:\n\n> BTW can git have a tag and a branch with the same name? If\n> not,...\n\nThis is \"Yes but\".\n\nYou can have a tag foo and branch foo.\n\n- \"git checkout foo\" would switch you to foo branch\n\n- Anything else that lets you use an abbreviated refname 'foo',\n e.g.\n\n . git branch newbranch foo\n . git log foo\n . git diff foo\n\n will scold you that 'foo' is ambiguous, while it does not\n outright fail, and takes the first match from the list defined\n in sha1_name.c (ref_fmt[]), so a tag wins over a branch. You\n can clarify yourself to avoid ambiguity like so:\n\n . git branch newbranch heads/foo ;# I mean \"branch from foo branch\"\n . git log tags/foo ;# \"show history starting at that tag\"\n"},{"id":"51805","messageId":"cb7bb73a0708290353iba0bdefl81a4a4e158be2fbf@mail.gmail.com","threadId":"9675","inReplyTo":"7v4piisolb.fsf@gitster.siamese.dyndns.org","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-29T10:53:15Z","receivedAt":"2007-08-29T10:53:15Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On 8/29/07, Junio C Hamano wrote:\n> \"Giuseppe Bilotta\" writes:\n>\n> > BTW can git have a tag and a branch with the same name? If\n> > not,...\n>\n> This is \"Yes but\".\n>\n> You can have a tag foo and branch foo.\n\n[snip]\n\n> You can clarify yourself to avoid ambiguity like so:\n>\n> . git branch newbranch heads/foo ;# I mean \"branch from foo branch\"\n> . git log tags/foo ;# \"show history starting at that tag\"\n\nOk. So assuming we import a svn repo which has a tag and a branch\ncalled 'name', and that there are post-tag commits in tags/name, how\ndo we call the stuff?\n\nWe could call 'name' both the (annotated) tag and the branch, but what\nname would we use for the branch created by post-tag commits?\n\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51847","messageId":"7vhcmip05g.fsf@gitster.siamese.dyndns.org","threadId":"9675","inReplyTo":"cb7bb73a0708290353iba0bdefl81a4a4e158be2fbf@mail.gmail.com","subject":"Re: git-svn tags and branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-08-29T20:15:55Z","receivedAt":"2007-08-29T20:15:55Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Giuseppe Bilotta\" writes:\n\n> On 8/29/07, Junio C Hamano wrote:\n>> \"Giuseppe Bilotta\" writes:\n>>\n>> > BTW can git have a tag and a branch with the same name? If\n>> > not,...\n>>\n>> This is \"Yes but\".\n>>\n>> You can have a tag foo and branch foo.\n>\n> [snip]\n>\n>> You can clarify yourself to avoid ambiguity like so:\n>>\n>> . git branch newbranch heads/foo ;# I mean \"branch from foo branch\"\n>> . git log tags/foo ;# \"show history starting at that tag\"\n>\n> Ok. So assuming we import a svn repo which has a tag and a branch\n> called 'name', and that there are post-tag commits in tags/name, how\n> do we call the stuff?\n>\n> We could call 'name' both the (annotated) tag and the branch, but what\n> name would we use for the branch created by post-tag commits?\n\nThat's the \"Yes but\" part. You need to know what you are doing.\n\nAs I said in the part you quoted, if you have branch foo and tag\nfoo, and if you are interested in talking about the tag 'foo',\nyou say \"tag/foo\". When you want to talk about the branch, you\nsay \"heads/foo\". Replace \"foo\" with \"name\" and I think you get\nyour answer.\n"},{"id":"51855","messageId":"cb7bb73a0708291406u5b5257fdh8d503e377209956b@mail.gmail.com","threadId":"9675","inReplyTo":"7vhcmip05g.fsf@gitster.siamese.dyndns.org","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-29T21:06:25Z","receivedAt":"2007-08-29T21:06:25Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"[did it again, sorry for the double-sent]\n\nOn 8/29/07, Junio C Hamano wrote:\n> As I said in the part you quoted, if you have branch foo and tag\n> foo, and if you are interested in talking about the tag 'foo',\n> you say \"tag/foo\". When you want to talk about the branch, you\n> say \"heads/foo\". Replace \"foo\" with \"name\" and I think you get\n> your answer.\n\nThe problem here is that you can have THREE things: the tag foo, the\nbranch foo, and the 'branch' under the tag foo, which is not the\nbranch foo.\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51857","messageId":"cb7bb73a0708291427k7b3a5de8y61b5562f45c73069@mail.gmail.com","threadId":"9675","inReplyTo":"7vy7fu9h9n.fsf@gitster.siamese.dyndns.org","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-29T21:27:07Z","receivedAt":"2007-08-29T21:27:07Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On 8/29/07, Junio C Hamano wrote:\n> \"Giuseppe Bilotta\" writes:\n>\n> > On 8/29/07, Junio C Hamano wrote:\n> >> As I said in the part you quoted, if you have branch foo and tag\n> >> foo, and if you are interested in talking about the tag 'foo',\n> >> you say \"tag/foo\". When you want to talk about the branch, you\n> >> say \"heads/foo\". Replace \"foo\" with \"name\" and I think you get\n> >> your answer.\n> >\n> > The problem here is that you can have THREE things: the tag foo, the\n> > branch foo, and the 'branch' under the tag foo, which is not the\n> > branch foo.\n>\n> What do you mean? \"refs/tags/foo\", \"refs/heads/foo\" and ...?\n>\n> You cannot have \"refs/tags/foo/bar\" if you have \"refs/tags/foo\".\n>\n\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51890","messageId":"20070830102115.GA17620@muzzle","threadId":"9675","inReplyTo":"faulrb$483$1@sea.gmane.org","subject":"Re: git-svn tags and branches","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2007-08-30T10:21:15Z","receivedAt":"2007-08-30T10:21:15Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Giuseppe Bilotta wrote:\n> Currently, git-svn imports svn tags as lightweight git tags.\n> I was susprised when I discovered this (from 'git describe'\n> failing and some helpful assistance on the IRC channel), so\n> I'm now wondering: is there a technical reason why they\n> aren't converted to annotated tags? If not, would it be\n> possible to implement this in git-svn, possibly with some\n> way to 'fix' existing git-svn repository?\n\nAs noted by other repliers, SVN tags can be moving targets just like\nbranches, and are treated as such by git-svn.\n\nI should note that tags in git can actually be updated like a branch\njust the same way, too, it's just not as easy to \"accidentally\" do.\n\nSo I'll add the ability to modify refs under the refs/tags/ namespace to\nmy git-svn TODO list (which is getting rather large). I also plan to\nsupport branches outside of the refs/remotes/ namespace so it's easier\nto use (clone, browse from gitweb) from bare repositories.\n\n> My second question concerns the uses of branche in git-svn,\n> but it might come from a not perfect understanding of the\n> branching mechanism in git (and yes, I've read the\n> documentation and Wiki pages).\n> \n> If I understand correctly, svn branches are imported in\n> git-svn as remote branches (refs/remote/*) and are\n> automatically updated on git-svn fetch or git-svn fetch-all.\n> \n> In my experiments, however, I've noticed the following\n> behaviour.\n> \n> git branch --track trunk remote/trunk\n> \n> git svn dcommit\n> \n> Now, master and remote/trunk point to the new roundtripped\n> changes, but the branch 'trunk' (in git) remains pointing to\n> the old remote/trunk head. I would have expected the --track\n> option to keep trunk in sync with remote/trunk ...\n> \n> Or am I missing something obvious?\n\nThe author of git-svn (myself) hasn't gotten around to supporting\n(or even looking at) git branch --track.\n\nRight now, dcommit only knows about HEAD and the remote it's committing\nto, nothing else. The config set by --track doesn't do anything\nfor git-svn.\n\nI really have a lot of catching up to do with all the new(er) things\nhappening in git. I learned git (what seems like) aeons ago have been\nmore or less content with what the plumbing offered back then. The past\nsix months of my life hasn't exactly left me with a lot of time or\nenergy for git, either; hopefully I'll have more time soon...\n\n-- \nEric Wong\n"},{"id":"51897","messageId":"cb7bb73a0708300444q73e12d72o665a8266c2a90f61@mail.gmail.com","threadId":"9675","inReplyTo":"20070830102115.GA17620@muzzle","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-30T11:44:35Z","receivedAt":"2007-08-30T11:44:35Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On 8/30/07, Eric Wong wrote:\n> As noted by other repliers, SVN tags can be moving targets just like\n> branches, and are treated as such by git-svn.\n>\n> I should note that tags in git can actually be updated like a branch\n> just the same way, too, it's just not as easy to \"accidentally\" do.\n>\n> So I'll add the ability to modify refs under the refs/tags/ namespace to\n> my git-svn TODO list (which is getting rather large). I also plan to\n> support branches outside of the refs/remotes/ namespace so it's easier\n> to use (clone, browse from gitweb) from bare repositories.\n\nThank you very much, that would be very appreciated.\n\nWhile we're at it: could you consider putting the svn-imported refs\nnot directly under remote? something like refs/remote/svn would be\nrather cleaner.\n\n> I really have a lot of catching up to do with all the new(er) things\n> happening in git. I learned git (what seems like) aeons ago have been\n> more or less content with what the plumbing offered back then. The past\n> six months of my life hasn't exactly left me with a lot of time or\n> energy for git, either; hopefully I'll have more time soon...\n\nI enormously appreciate the efforts you've put into git-svn so far, it\nhas been quite a refreshing change from having to way eons every time\nI had to commit something, while still giving me the ability to keep\nmy work nicely in sync with the upstream repo.\n\nI've considered tackling these minor issues myself, but my\nunderstanding of git's internals is most definitely not yet adequate,\nso I haven't been able to do any hacking yet.\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"},{"id":"51905","messageId":"20070830122514.GF5050@xp.machine.xx","threadId":"9675","inReplyTo":"cb7bb73a0708300444q73e12d72o665a8266c2a90f61@mail.gmail.com","subject":"Re: git-svn tags and branches","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2007-08-30T12:25:14Z","receivedAt":"2007-08-30T12:25:14Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Thu, Aug 30, 2007 at 01:44:35PM +0200, Giuseppe Bilotta wrote:\n> On 8/30/07, Eric Wong wrote:\n> > As noted by other repliers, SVN tags can be moving targets just like\n> > branches, and are treated as such by git-svn.\n> >\n> > I should note that tags in git can actually be updated like a branch\n> > just the same way, too, it's just not as easy to \"accidentally\" do.\n> >\n> > So I'll add the ability to modify refs under the refs/tags/ namespace to\n> > my git-svn TODO list (which is getting rather large). I also plan to\n> > support branches outside of the refs/remotes/ namespace so it's easier\n> > to use (clone, browse from gitweb) from bare repositories.\n> \n> Thank you very much, that would be very appreciated.\n> \n> While we're at it: could you consider putting the svn-imported refs\n> not directly under remote? something like refs/remote/svn would be\n> rather cleaner.\n> \n\nDid you have a look at the --prefix option mentioned in the manpage? I\nthink it does what you want.\n\n-Peter\n"},{"id":"51919","messageId":"cb7bb73a0708300901j6ae83730p20d272c317de9116@mail.gmail.com","threadId":"9675","inReplyTo":"20070830122514.GF5050@xp.machine.xx","subject":"Re: git-svn tags and branches","fromName":"Giuseppe Bilotta","fromEmail":"giuseppe.bilotta@gmail.com","sentAt":"2007-08-30T16:01:46Z","receivedAt":"2007-08-30T16:01:46Z","isPatch":false,"sender":{"key":"giuseppe.bilotta@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1464?v=4"},"body":"On 8/30/07, Peter Baumann wrote:\n> On Thu, Aug 30, 2007 at 01:44:35PM +0200, Giuseppe Bilotta wrote:\n> > While we're at it: could you consider putting the svn-imported refs\n> > not directly under remote? something like refs/remote/svn would be\n> > rather cleaner.\n>\n> Did you have a look at the --prefix option mentioned in the manpage? I\n> think it does what you want.\n\nUh, it must have escaped me, thanks.\n\n(Still, it would make sense to have a non-empty default.)\n\n-- \nGiuseppe \"Oblomov\" Bilotta\n"}]}