git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: stgit: No patches to pop

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 11, 2006, 22:54 UTC
Message-ID
<200612112354.53124.jnareb@gmail.com>
In-Reply-To
<b0943d9e0612111426s3e0c671eqca31558e47d4348b@mail.gmail.com>
Catalin Marinas wrote:
Show 30 quoted lines
> On 11/12/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> Catalin Marinas wrote:
>>
>>>> I also get things like:
>>>>
>>>> % stg pop second
>>>> popping patch "third"... done
>>>> Now at patch "second"
>>>
>>> In version 0.11, the "pop" command is equivalent to "goto". I changed
>>> this in the latest version (in the StGIT repository) so that "pop
>>> <patch>" tries to only extract that patch from the stack by popping
>>> all the patches to the given one and pushing them back without the one
>>> you specified. It also supports patch ranges (i.e. patch1..patch4).
>>
>> That is kind of strange. Pop should work like pop does, for example
>> the one in Perl or Python, removing n elements from the stack of applied
>> patches. Not work as "float <patch>"...
> 
> Probably I wasn't clear enough. The "pop" operations are as follows:
> 
> 1. "stg pop" only removes the top patch from the applied patches
> 2. "stg pop <patch>.." is equivalent to popping all patches to <patch>
> (including the latter)
> 3. "stg pop <patch>" is equivalent to "stg float <patch>; stg pop".
> 4. "stg pop <patch list or range>" is equivalent to "stg float <patch
> list or range>; stg pop <all the patches in the list or range>"
> 
> These feature was Yann's idea and I find it to be more in line with
> the "push" command.

Nice, and easy to understand. By the way, the same works with "stg push", doesn't it?

-- 
Jakub Narebski
Previous: Catalin Marinas
Message 6 of 6 in “stgit: No patches to pop”
  1. Bahadir BalbanDec 11, 2006
  2. Catalin MarinasDec 11, 2006
  3. Jakub NarebskiDec 11, 2006
  4. Bahadir BalbanDec 11, 2006
  5. Catalin MarinasDec 12, 2006
  6. Jakub NarebskiDec 11, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.