From: Michael Stapelberg <michael+sup@stapelberg.de>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>,
sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [Turnsole] Experimental GPG signature verification
Date: Sun, 18 Mar 2012 23:45:52 +0100 [thread overview]
Message-ID: <1332110718-sup-6603@stapelberg.de> (raw)
In-Reply-To: <1331733289-sup-7680@stapelberg.de>
Hi Nicolas,
Excerpts from Michael Stapelberg's message of 2012-03-14 14:55:55 +0100:
> > So there is no way to compose any message when merging your branch?
> That might be true. To be honest, I don’t compose messages in heliotrope yet,
> otherwise, I won’t have them in sup (my fallback). Yes, the situation sucks big
> time.
This is fixed now with commit https://github.com/mstap/turnsole/commit/2817026
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2012-03-18 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 18:28 Michael Stapelberg
2012-03-14 13:13 ` Nicolas Pouillard
2012-03-14 13:31 ` Michael Stapelberg
2012-03-14 13:38 ` Nicolas Pouillard
2012-03-14 13:55 ` Michael Stapelberg
2012-03-18 22:45 ` Michael Stapelberg [this message]
2012-03-19 7:53 ` Nicolas Pouillard
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=1332110718-sup-6603@stapelberg.de \
--to=michael+sup@stapelberg.de \
--cc=nicolas.pouillard@gmail.com \
--cc=sup-devel@rubyforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox