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

Re: Recover from a bad push in StGit

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Aug 21, 2006, 15:55 UTC
Message-ID
<b0943d9e0608210855m71c29a21y3d4941ec721e0737@mail.gmail.com>
In-Reply-To
<200608211703.59873.robin.rosenberg.lists@dewire.com>
On 21/08/06, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
Show 5 quoted lines
> måndag 21 augusti 2006 11:35 skrev Catalin Marinas:
> > "stg push --undo" (the same option for "refresh"; maybe I should add a
> > separate "undo" command) resets the local changes and it restores the
> Not necessarily, but a hint about --undo when push/pop fail would have
> helped me.

It is in the "stg help push" output but I could just display it when the conflict happened.

Show 6 quoted lines
> > original boundaries of the patch (no information is lost). You could
> > use the latest snapshot as it has some bug-fixes from release 0.10.
>
> Does refresh --undo make me see the state of the patch like it was before last
> refresh, ie. stgit remembers the history of my patces? I thought it dropped
> the references as obsolete.

The references before the last command are stored and they can be obtained by "stg id <patch>//(bottom|top).old". As long as you haven't run a git prune on your repository, you should be able to undo the refresh.

I'm (slowly) working on patch history support using reflogs and (when ready) you should be able to retrieve a previous state of the patch as long as you haven't pruned your GIT repository.

-- 
Catalin
Previous: Robin Rosenberg
Message 5 of 5 in “Recover from a bad push in StGit”
  1. Robin RosenbergAug 18, 2006
  2. Robin RosenbergAug 19, 2006
  3. Catalin MarinasAug 21, 2006
  4. Robin RosenbergAug 21, 2006
  5. Catalin MarinasAug 21, 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.