From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] gpg signing issue
Date: Thu, 28 Feb 2008 09:09:55 -0800 [thread overview]
Message-ID: <1204218343-sup-313@south> (raw)
In-Reply-To: <1204138293-sup-8382@aconcagua>
Reformatted excerpts from Jan Spakula's message of 2008-02-27:
> Yes, both fixes work. (Didn't try them simultaneusly though.)
Ok, I'm going to merge this into both next and master.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-02-28 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 3:40 Jan Spakula
2008-02-27 8:39 ` Nicolas Pouillard
2008-02-27 17:50 ` William Morgan
2008-02-27 18:56 ` Jan Spakula
2008-02-28 17:09 ` William Morgan [this message]
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=1204218343-sup-313@south \
--to=wmorgan-sup@masanjin.net \
/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