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

Re: stgit: cannot push a patch - Python trace dump

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Sep 15, 2006, 14:33 UTC
Message-ID
<b0943d9e0609150733v6cbe465esfd8d2b598c496768@mail.gmail.com>
In-Reply-To
<450AB81F.2090305@intel.com>
On 15/09/06, Auke Kok <auke-jan.h.kok@intel.com> wrote:
Show 7 quoted lines
> Catalin Marinas wrote:
> > Thanks, I fixed StGIT to cope with this and I'll update the repository
> > and snapshot tonight (which, BTW, will contain the initial support for
> > patch history tracking).
>
> awesome and awesome, allthough I have no idea what that (patch history
> tracking) is about :)

It keeps the history of all the patch modifications (like refresh, push) so that you can get previous versions if something went wrong. It's like having many small commits reflecting the changes to a patch. These commits are totally separate from the main patch commit (so that an StGIT repository is still compatible with GIT) but you can access them with "stg log [--graphical] <patch>". The --graphical option will automatically invoke gitk.

-- 
Catalin
Previous: Auke Kok
Message 4 of 4 in “stgit: cannot push a patch - Python trace dump”
  1. Auke KokSep 15, 2006
  2. Catalin MarinasSep 15, 2006
  3. Auke KokSep 15, 2006
  4. Catalin MarinasSep 15, 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.