From: Pavel Roskin <proski@gnu.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: Signing by StGIT broken
Date: Fri, 11 Jan 2008 23:58:03 -0500 [thread overview]
Message-ID: <1200113883.26841.18.camel@rd> (raw)
In-Reply-To: <20080110074252.GA18629@diana.vm.bytemark.co.uk>
On Thu, 2008-01-10 at 08:42 +0100, Karl Hasselström wrote:
> On 2008-01-09 21:53:16 -0500, Pavel Roskin wrote:
>
> > "stg edit --sign" is not working anymore. It was working in version
> > 0.14.
>
> Thanks for the report and the detailed analysis. I'll write a test and
> fix it (but not quite immediately, so feel free to beat me to it).
The fix below appears to work (thus making it a self-signing patch :))
but with my modest Python experience it absolutely needs to be reviewed.
I don't even know how to wrap the long line without making it look
misleading.
No testsuite fixes, sorry. But the existing testsuite passes.
Fix "stg edit --sign"
Signed-off-by: Pavel Roskin <proski@gnu.org>
---
stgit/commands/edit.py | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/stgit/commands/edit.py b/stgit/commands/edit.py
index b9699d5..650d5a3 100644
--- a/stgit/commands/edit.py
+++ b/stgit/commands/edit.py
@@ -90,7 +90,10 @@ def __update_patch(pname, text, options):
bottom = patch.get_bottom()
top = patch.get_top()
- message, author_name, author_email, author_date, diff = parse_patch(text)
+ if text:
+ message, author_name, author_email, author_date, diff = parse_patch(text)
+ else:
+ message = author_name = author_email = author_date = diff = None
out.start('Updating patch "%s"' % pname)
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-01-12 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 2:53 Signing by StGIT broken Pavel Roskin
2008-01-10 7:42 ` Karl Hasselström
2008-01-12 4:58 ` Pavel Roskin [this message]
2008-01-18 3:51 ` Karl Hasselström
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=1200113883.26841.18.camel@rd \
--to=proski@gnu.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).