{"thread":{"id":"43206","subject":"stgit: No patches to pop","startedAt":"2006-12-11T14:32:46Z","lastAt":"2006-12-12T09:10:00Z","messageCount":6,"participants":["Bahadir Balban","Catalin Marinas","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"294030","messageId":"7ac1e90c0612110632x56a2917cu4db33e47923f34c2@mail.gmail.com","threadId":"43206","inReplyTo":null,"subject":"stgit: No patches to pop","fromName":"Bahadir Balban","fromEmail":"bahadir.balban@gmail.com","sentAt":"2006-12-11T14:32:46Z","receivedAt":"2006-12-11T14:32:46Z","isPatch":false,"sender":{"key":"bahadir.balban@gmail.com","avatar":null},"body":"Hi,\n\nI've just recently started using stgit (v0.11, git v1.4.3.4). On a\ntest repository, I do:\n\n% stg applied\nfirst\nsecond\nthird\n\nbut when I pop I get:\n\n% stg pop\nstg pop: No patches to pop\n\nI also get things like:\n\n% stg pop second\npopping patch \"third\"... done\nNow at patch \"second\"\n\nIs this normal?\n\nThanks,\n"},{"id":"294516","messageId":"tnxpsaqwgxl.fsf@arm.com","threadId":"43206","inReplyTo":"7ac1e90c0612110632x56a2917cu4db33e47923f34c2@mail.gmail.com","subject":"Re: stgit: No patches to pop","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@arm.com","sentAt":"2006-12-11T16:11:50Z","receivedAt":"2006-12-11T16:11:50Z","isPatch":false,"sender":{"key":"catalin.marinas@arm.com","avatar":null},"body":"\"Bahadir Balban\" wrote:\n> I've just recently started using stgit (v0.11, git v1.4.3.4). On a\n> test repository, I do:\n>\n> % stg applied\n> first\n> second\n> third\n>\n> but when I pop I get:\n>\n> % stg pop\n> stg pop: No patches to pop\n\nCan you write a list of commands or script so that I can easily\nreproduce this? It works OK for me.\n\n> I also get things like:\n>\n> % stg pop second\n> popping patch \"third\"... done\n> Now at patch \"second\"\n\nIn version 0.11, the \"pop\" command is equivalent to \"goto\". I changed\nthis in the latest version (in the StGIT repository) so that \"pop\n\" tries to only extract that patch from the stack by popping\nall the patches to the given one and pushing them back without the one\nyou specified. It also supports patch ranges (i.e. patch1..patch4).\n\n-- \n"},{"id":"298652","messageId":"elk0c3$ovu$1@sea.gmane.org","threadId":"43206","inReplyTo":"tnxpsaqwgxl.fsf@arm.com","subject":"Re: stgit: No patches to pop","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-12-11T16:20:34Z","receivedAt":"2006-12-11T16:20:34Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Catalin Marinas wrote:\n\n>> I also get things like:\n>>\n>> % stg pop second\n>> popping patch \"third\"... done\n>> Now at patch \"second\"\n> \n> In version 0.11, the \"pop\" command is equivalent to \"goto\". I changed\n> this in the latest version (in the StGIT repository) so that \"pop\n> \" tries to only extract that patch from the stack by popping\n> all the patches to the given one and pushing them back without the one\n> you specified. It also supports patch ranges (i.e. patch1..patch4).\n\nThat is kind of strange. Pop should work like pop does, for example\nthe one in Perl or Python, removing n elements from the stack of applied\npatches. Not work as \"float \"...\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n"},{"id":"298326","messageId":"7ac1e90c0612110905x3f1632b9v17bb14e810715cbf@mail.gmail.com","threadId":"43206","inReplyTo":"elk0c3$ovu$1@sea.gmane.org","subject":"Re: stgit: No patches to pop","fromName":"Bahadir Balban","fromEmail":"bahadir.balban@gmail.com","sentAt":"2006-12-11T17:05:20Z","receivedAt":"2006-12-11T17:05:20Z","isPatch":false,"sender":{"key":"bahadir.balban@gmail.com","avatar":null},"body":"On 12/11/06, Jakub Narebski wrote:\n> That is kind of strange. Pop should work like pop does, for example\n> the one in Perl or Python, removing n elements from the stack of applied\n> patches. Not work as \"float \"...\n> --\n> Jakub Narebski\n> Warsaw, Poland\n> ShadeHawk on #git\n\nAs a new user my first expectation was as Catalin has revised. If it's\ngoing to stay as in 0.11 at least it would be nice to have it\ndescribed in the wiki.\n\nThanks,\n"},{"id":"296722","messageId":"200612112354.53124.jnareb@gmail.com","threadId":"43206","inReplyTo":"b0943d9e0612111426s3e0c671eqca31558e47d4348b@mail.gmail.com","subject":"Re: stgit: No patches to pop","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-12-11T22:54:52Z","receivedAt":"2006-12-11T22:54:52Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Catalin Marinas wrote:\n> On 11/12/06, Jakub Narebski wrote:\n>> Catalin Marinas wrote:\n>>\n>>>> I also get things like:\n>>>>\n>>>> % stg pop second\n>>>> popping patch \"third\"... done\n>>>> Now at patch \"second\"\n>>>\n>>> In version 0.11, the \"pop\" command is equivalent to \"goto\". I changed\n>>> this in the latest version (in the StGIT repository) so that \"pop\n>>> \" tries to only extract that patch from the stack by popping\n>>> all the patches to the given one and pushing them back without the one\n>>> you specified. It also supports patch ranges (i.e. patch1..patch4).\n>>\n>> That is kind of strange. Pop should work like pop does, for example\n>> the one in Perl or Python, removing n elements from the stack of applied\n>> patches. Not work as \"float \"...\n> \n> Probably I wasn't clear enough. The \"pop\" operations are as follows:\n> \n> 1. \"stg pop\" only removes the top patch from the applied patches\n> 2. \"stg pop ..\" is equivalent to popping all patches to \n> (including the latter)\n> 3. \"stg pop \" is equivalent to \"stg float ; stg pop\".\n> 4. \"stg pop \" is equivalent to \"stg float list or range>; stg pop \"\n> \n> These feature was Yann's idea and I find it to be more in line with\n> the \"push\" command.\n\nNice, and easy to understand. By the way, the same works with \"stg push\",\ndoesn't it?\n\n-- \nJakub Narebski\n"},{"id":"296193","messageId":"tnxlkldwkd3.fsf@arm.com","threadId":"43206","inReplyTo":"7ac1e90c0612110905x3f1632b9v17bb14e810715cbf@mail.gmail.com","subject":"Re: stgit: No patches to pop","fromName":"Catalin Marinas","fromEmail":"catalin.marinas@arm.com","sentAt":"2006-12-12T09:10:00Z","receivedAt":"2006-12-12T09:10:00Z","isPatch":false,"sender":{"key":"catalin.marinas@arm.com","avatar":null},"body":"\"Bahadir Balban\" wrote:\n> On 12/11/06, Jakub Narebski wrote:\n>> That is kind of strange. Pop should work like pop does, for example\n>> the one in Perl or Python, removing n elements from the stack of applied\n>> patches. Not work as \"float \"...\n>> --\n>> Jakub Narebski\n>> Warsaw, Poland\n>> ShadeHawk on #git\n>\n> As a new user my first expectation was as Catalin has revised. If it's\n> going to stay as in 0.11 at least it would be nice to have it\n> described in the wiki.\n\nIt was already modified in the StGIT repository and I am won't revert\nit to the 0.11 functionality. Please feel free to modify the wiki\n(which is really out of date - \"stg help \" has more\nup-to-date information).\n\n-- \n"}]}