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

Re: Bug in StackedGit

From
Vitaly V. Ch <vitaly.v.ch@gmail.com>
Date
Apr 15, 2008, 11:21 UTC
Message-ID
<6efe08af0804150421p2d3dfbd2uf327c933b385bc38@mail.gmail.com>
In-Reply-To
<b0943d9e0804150413h5268532ey2f2ee33fca1be783@mail.gmail.com>

I want revert some patch to one of previous version like I can do same in bzr loom.

\\wbr Vitaly Chernookiy

On Tue, Apr 15, 2008 at 11:13 AM, Catalin Marinas <catalin.marinas@gmail.com> wrote:

Show 10 quoted lines
> On 15/04/2008, Vitaly V. Ch <vitaly.v.ch@gmail.com> wrote:
>  > after stg commit all patch history is loss. It's sucks.
>
>  Why do you need the patch history after "stg commit"? This command is
>  meant to take the patches out of StGIT control and freeze them in the
>  Git repository history.
>
>  --
>  Catalin
>
Previous: Catalin Marinas
Message 6 of 6 in “Fwd: Bug in StackedGit”
  1. Vitaly V. ChApr 15, 2008
  2. Karl HasselströmApr 15, 2008
  3. Vitaly V. ChApr 15, 2008
  4. Karl HasselströmApr 15, 2008
  5. Catalin MarinasApr 15, 2008
  6. Vitaly V. ChApr 15, 2008

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.