All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: git@vger.kernel.org
Subject: Re: stgit: cannot push a patch - Python trace dump
Date: Fri, 15 Sep 2006 09:58:48 +0100	[thread overview]
Message-ID: <tnxwt855wvr.fsf@arm.com> (raw)
In-Reply-To: <450A3524.5040403@intel.com> (Auke Kok's message of "Thu, 14 Sep 2006 22:07:48 -0700")

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).

-- 
Catalin

  reply	other threads:[~2006-09-15  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  5:07 stgit: cannot push a patch - Python trace dump Auke Kok
2006-09-15  8:58 ` Catalin Marinas [this message]
2006-09-15 14:26   ` Auke Kok
2006-09-15 14:33     ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tnxwt855wvr.fsf@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.