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

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

From
AKAuke Kok <auke-jan.h.kok@intel.com>
Date
Sep 15, 2006, 14:26 UTC
Message-ID
<450AB81F.2090305@intel.com>
In-Reply-To
<tnxwt855wvr.fsf@arm.com>
Catalin Marinas wrote:
Show 11 quoted lines
> Auke Kok <auke-jan.h.kok@intel.com> wrote:
>> I'm preparing patches for upstream and am haunted by an apparent
>> patch breaking stg. The problem appears to be one or more of my
>> patches breaking a push:
> [...]
>> I've been abusing stg by leaving the commit messages empty so I
>> assume that that's the cause here, or related to the problem.
> 
> 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 :)

Auke
Previous: Catalin MarinasNext: Catalin Marinas
Message 3 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.