{"thread":{"id":"31800","subject":"[BUG?] git-subtree behavior when the -P tree is removed and recreated","startedAt":"2012-10-13T13:47:08Z","lastAt":"2013-01-01T01:43:13Z","messageCount":7,"participants":["Tomi Belan","Junio C Hamano","greened@obbligato.org"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"201081","messageId":"CACUV5ofmuUku=byR1_+Cq+g0SdzqZbH1Z1tPfQf4eNABVyYb_Q@mail.gmail.com","threadId":"31800","inReplyTo":null,"subject":"[BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"Tomi Belan","fromEmail":"tomi.belan@gmail.com","sentAt":"2012-10-13T13:47:08Z","receivedAt":"2012-10-13T13:47:08Z","isPatch":false,"sender":{"key":"tomi.belan@gmail.com","avatar":null},"body":"Hello folks,\n\nI think I might've found a bug in git-subtree: I have a repository\ncontaining a directory \"foo\". I'd like to use its code in other\nprojects, so I want to split it off into its own repository with\ngit-subtree. But it doesn't work as it should. I found out that long\nago, my repository contained an unrelated directory also called \"foo\"\nwhich has since been deleted.\n\nSteps to reproduce (after installing git-subtree from contrib):\ngit init repo\ncd repo\nmkdir foo; touch foo/v1\ngit add -A .; git commit -m v1\nrm -rf foo; touch v2\ngit add -A .; git commit -m v2\nmkdir foo; touch foo/v3\ngit add -A .; git commit -m v3\ngit subtree split -P foo -b splitfoo --annotate=\"split \"\n\nWhat should happen: Either (A) splitfoo only contains \"split v3\", or\n(B) splitfoo contains \"split v1\" and \"split v3\"\n\nWhat happens instead: The parent of \"split v3\" is \"v2\", so splitfoo's\nfull history is: \"v1\" -> \"v2\" -> \"split v3\".\n\nGit version: 1.7.12.2\n\nBonus questions:\n- which is the intended behavior, (A) or (B)?\n- if it's (B), how do I convince git-subtree to do (A) once this bug\ngets fixed? (I might be getting too far ahead of myself here...)\n\nTomi\n"},{"id":"201656","messageId":"CACUV5odffQoCxr=hTuP+S+DU4+6qD7y=YkTCN3iRr7rjar1bLQ@mail.gmail.com","threadId":"31800","inReplyTo":"CACUV5ofmuUku=byR1_+Cq+g0SdzqZbH1Z1tPfQf4eNABVyYb_Q@mail.gmail.com","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"Tomi Belan","fromEmail":"tomi.belan@gmail.com","sentAt":"2012-10-21T21:18:08Z","receivedAt":"2012-10-21T21:18:08Z","isPatch":false,"sender":{"key":"tomi.belan@gmail.com","avatar":null},"body":"This probably got lost in the mail. Could somebody familiar with\ngit-subtree take a look?\nTomi\n\nOn Sat, Oct 13, 2012 at 3:47 PM, Tomi Belan wrote:\n>\n> Hello folks,\n>\n> I think I might've found a bug in git-subtree: I have a repository\n> containing a directory \"foo\". I'd like to use its code in other\n> projects, so I want to split it off into its own repository with\n> git-subtree. But it doesn't work as it should. I found out that long\n> ago, my repository contained an unrelated directory also called \"foo\"\n> which has since been deleted.\n>\n> Steps to reproduce (after installing git-subtree from contrib):\n> git init repo\n> cd repo\n> mkdir foo; touch foo/v1\n> git add -A .; git commit -m v1\n> rm -rf foo; touch v2\n> git add -A .; git commit -m v2\n> mkdir foo; touch foo/v3\n> git add -A .; git commit -m v3\n> git subtree split -P foo -b splitfoo --annotate=\"split \"\n>\n> What should happen: Either (A) splitfoo only contains \"split v3\", or\n> (B) splitfoo contains \"split v1\" and \"split v3\"\n>\n> What happens instead: The parent of \"split v3\" is \"v2\", so splitfoo's\n> full history is: \"v1\" -> \"v2\" -> \"split v3\".\n>\n> Git version: 1.7.12.2\n>\n> Bonus questions:\n> - which is the intended behavior, (A) or (B)?\n> - if it's (B), how do I convince git-subtree to do (A) once this bug\n> gets fixed? (I might be getting too far ahead of myself here...)\n>\n> Tomi\n"},{"id":"204444","messageId":"CACUV5ocT56iOS3dZsJ4JLo70o1HJv2TSrvBHE646SyQVmOuYRg@mail.gmail.com","threadId":"31800","inReplyTo":"CACUV5odffQoCxr=hTuP+S+DU4+6qD7y=YkTCN3iRr7rjar1bLQ@mail.gmail.com","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"Tomi Belan","fromEmail":"tomi.belan@gmail.com","sentAt":"2012-12-03T10:39:36Z","receivedAt":"2012-12-03T10:39:36Z","isPatch":false,"sender":{"key":"tomi.belan@gmail.com","avatar":null},"body":"Another bump. I reported this back in October, but there hasn't been\nany response yet...\n\nNote that the bug is still present in git 1.8.0.1.\n\nTomi\n\nOn Sun, Oct 21, 2012 at 11:18 PM, Tomi Belan wrote:\n> This probably got lost in the mail. Could somebody familiar with\n> git-subtree take a look?\n> Tomi\n>\n> On Sat, Oct 13, 2012 at 3:47 PM, Tomi Belan wrote:\n>>\n>> Hello folks,\n>>\n>> I think I might've found a bug in git-subtree: I have a repository\n>> containing a directory \"foo\". I'd like to use its code in other\n>> projects, so I want to split it off into its own repository with\n>> git-subtree. But it doesn't work as it should. I found out that long\n>> ago, my repository contained an unrelated directory also called \"foo\"\n>> which has since been deleted.\n>>\n>> Steps to reproduce (after installing git-subtree from contrib):\n>> git init repo\n>> cd repo\n>> mkdir foo; touch foo/v1\n>> git add -A .; git commit -m v1\n>> rm -rf foo; touch v2\n>> git add -A .; git commit -m v2\n>> mkdir foo; touch foo/v3\n>> git add -A .; git commit -m v3\n>> git subtree split -P foo -b splitfoo --annotate=\"split \"\n>>\n>> What should happen: Either (A) splitfoo only contains \"split v3\", or\n>> (B) splitfoo contains \"split v1\" and \"split v3\"\n>>\n>> What happens instead: The parent of \"split v3\" is \"v2\", so splitfoo's\n>> full history is: \"v1\" -> \"v2\" -> \"split v3\".\n>>\n>> Git version: 1.7.12.2\n>>\n>> Bonus questions:\n>> - which is the intended behavior, (A) or (B)?\n>> - if it's (B), how do I convince git-subtree to do (A) once this bug\n>> gets fixed? (I might be getting too far ahead of myself here...)\n>>\n>> Tomi\n"},{"id":"205193","messageId":"CACUV5odJx1+47ggOAppN7whJhLABrRP-3mRWo8adQqbxF4mA5A@mail.gmail.com","threadId":"31800","inReplyTo":"877gozuooz.fsf@pctrast.inf.ethz.ch","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"Tomi Belan","fromEmail":"tomi.belan@gmail.com","sentAt":"2012-12-19T15:40:03Z","receivedAt":"2012-12-19T15:40:03Z","isPatch":false,"sender":{"key":"tomi.belan@gmail.com","avatar":null},"body":"Thanks. Here's one more bump. Avery? David?\n\n(Apologies if my bumping is annoying -- because there's no bug\ntracker, it feels like the bug will be lost in the ML archives forever\nunless I keep calling attention to it. How can I help to get this\nissue fixed?)\n\nTomi\n\nOn Mon, Dec 3, 2012 at 4:42 PM, Thomas Rast wrote:\n>\n> Tomi Belan writes:\n>\n> > Another bump. I reported this back in October, but there hasn't been\n> > any response yet...\n> >\n> > Note that the bug is still present in git 1.8.0.1.\n>\n> Probably it would be a good idea to bring it to the attention of people\n> who have worked on it: Avery and David (cc'd).\n>\n> >> On Sat, Oct 13, 2012 at 3:47 PM, Tomi Belan wrote:\n> >>>\n> >>> Hello folks,\n> >>>\n> >>> I think I might've found a bug in git-subtree: I have a repository\n> >>> containing a directory \"foo\". I'd like to use its code in other\n> >>> projects, so I want to split it off into its own repository with\n> >>> git-subtree. But it doesn't work as it should. I found out that long\n> >>> ago, my repository contained an unrelated directory also called \"foo\"\n> >>> which has since been deleted.\n> >>>\n> >>> Steps to reproduce (after installing git-subtree from contrib):\n> >>> git init repo\n> >>> cd repo\n> >>> mkdir foo; touch foo/v1\n> >>> git add -A .; git commit -m v1\n> >>> rm -rf foo; touch v2\n> >>> git add -A .; git commit -m v2\n> >>> mkdir foo; touch foo/v3\n> >>> git add -A .; git commit -m v3\n> >>> git subtree split -P foo -b splitfoo --annotate=\"split \"\n> >>>\n> >>> What should happen: Either (A) splitfoo only contains \"split v3\", or\n> >>> (B) splitfoo contains \"split v1\" and \"split v3\"\n> >>>\n> >>> What happens instead: The parent of \"split v3\" is \"v2\", so splitfoo's\n> >>> full history is: \"v1\" -> \"v2\" -> \"split v3\".\n> >>>\n> >>> Git version: 1.7.12.2\n> >>>\n> >>> Bonus questions:\n> >>> - which is the intended behavior, (A) or (B)?\n> >>> - if it's (B), how do I convince git-subtree to do (A) once this bug\n> >>> gets fixed? (I might be getting too far ahead of myself here...)\n> >>>\n> >>> Tomi\n>\n> --\n> Thomas Rast\n> trast@{inf,student}.ethz.ch\n"},{"id":"205194","messageId":"7v8v8uav8t.fsf@alter.siamese.dyndns.org","threadId":"31800","inReplyTo":"CACUV5odJx1+47ggOAppN7whJhLABrRP-3mRWo8adQqbxF4mA5A@mail.gmail.com","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-12-19T15:59:14Z","receivedAt":"2012-12-19T15:59:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Tomi Belan writes:\n\n> Thanks. Here's one more bump. Avery? David?\n\nThanks for your persistence.\n\nI am moderately dissapointed by the inaction on the subtree part so\nfar. It was merged hoping that it will have more exposure to the\nend-users if it were in my tree, and it obviously is gettng that,\nbut the people involved in the subtree part does not seem to be\nholding their end of the bargain.\n\nI am seriously considering to remove it from the contrib/ area of my\ntree if we do not see any response. The contrib/ area is not meant\nto be a dumping ground for abandoned WIP.\n\nMaybe it is a seasonal thing, just before the holiday season, but\nthis has been unresponded for a couple of months, not even with a\n\"That combination is not supported\", or \"Thanks for a bug report\".\n\nGrumpy.\n"},{"id":"205721","messageId":"87623h4r5y.fsf@waller.obbligato.org","threadId":"31800","inReplyTo":"CACUV5odJx1+47ggOAppN7whJhLABrRP-3mRWo8adQqbxF4mA5A@mail.gmail.com","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"","fromEmail":"greened@obbligato.org","sentAt":"2013-01-01T01:40:09Z","receivedAt":"2013-01-01T01:40:09Z","isPatch":false,"sender":{"key":"greened@obbligato.org","avatar":"https://avatars.githubusercontent.com/u/5291869?v=4"},"body":"Tomi Belan writes:\n\n> Thanks. Here's one more bump. Avery? David?\n\nI don't know how this is supposed to work, unfortunately. I'm still in\nthe middle of learning the code...\n\n -David\n"},{"id":"205720","messageId":"871ue54r0u.fsf@waller.obbligato.org","threadId":"31800","inReplyTo":"7v8v8uav8t.fsf@alter.siamese.dyndns.org","subject":"Re: [BUG?] git-subtree behavior when the -P tree is removed and recreated","fromName":"","fromEmail":"greened@obbligato.org","sentAt":"2013-01-01T01:43:13Z","receivedAt":"2013-01-01T01:43:13Z","isPatch":false,"sender":{"key":"greened@obbligato.org","avatar":"https://avatars.githubusercontent.com/u/5291869?v=4"},"body":"Junio C Hamano writes:\n\n> Maybe it is a seasonal thing, just before the holiday season, but\n> this has been unresponded for a couple of months, not even with a\n> \"That combination is not supported\", or \"Thanks for a bug report\".\n\nI did finally see this message. I totally admit that I've been pretty\nabsent. It just happens that I have a ton of paid work to do and\nvoluteer work unfortunately comes last, after family and after paid\nwork.\n\nFor this bug I honestly don't know what is supposed to happen. I'm\nstill learning the code. It's a bit of a shell-script mess to be\nhonest, very hard to follow. That's why it's still in contrib/\nand will remain so for a while.\n\nI am more than happy for others to jump in and help out. I'm not a\ngatekeeper.\n\n -David\n"}]}