From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] github patches
Date: Mon, 30 May 2011 23:57:11 +0100 [thread overview]
Message-ID: <1306794197-sup-949@whisper> (raw)
I thought I'd have a poke around github for useful patches that haven't
been applied, I've found a few. Big-ish ones (like the account selector)
are getting their own branch, but I can't be bothered doing that for
every single patch, so I've stated a branch called "github_patches" to
put a few small ones in.
There's one I'm not sure about, any feedback welcome:
https://github.com/mavam/sup/commit/cbc577609dea6cb058aaf39811678f9d34fd1848
This allows the startup hook to affect the sent source and draft source.
I wonder if any startup hooks would rely on the sent source and draft
source being set already?
Hamish Downer
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-05-30 23:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1306794197-sup-949@whisper \
--to=dmishd@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