From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Beginning to use async.el to help Gnus' interactivity
Date: Thu, 19 Jul 2012 09:36:08 -0400 [thread overview]
Message-ID: <87vchjhnzr.fsf@lifelogs.com> (raw)
In-Reply-To: <87mx2w4v5i.fsf@dod.no> (Steinar Bang's message of "Wed, 18 Jul 2012 23:27:37 +0200")
On Wed, 18 Jul 2012 23:27:37 +0200 Steinar Bang <sb@dod.no> wrote:
>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>> Contact me off-list for write access. Same for anyone who believes they
>> need it. I'd prefer more developers to more patches :)
SB> One possibility would be to create a git branch, push it to a repo on
SB> github, and then Ted can add that repo as a remote, fetch the branch
SB> from that remote, and then merge and push.
Sure, but it's still work for someone to review the diff and merge. I
gave John commit access so he should be OK.
Ted
prev parent reply other threads:[~2012-07-19 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 5:31 John Wiegley
2012-07-09 5:22 ` Carson Chittom
2012-07-18 14:03 ` Ted Zlatanov
2012-07-18 18:58 ` John Wiegley
2012-07-18 19:23 ` Ted Zlatanov
2012-07-18 21:27 ` Steinar Bang
2012-07-19 13:36 ` Ted Zlatanov [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=87vchjhnzr.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).