From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: auth-source.el request: NS port needs Mac OS X keychain functions
Date: Sun, 27 Mar 2011 09:14:35 -0500 [thread overview]
Message-ID: <87k4fk8xbo.fsf@lifelogs.com> (raw)
In-Reply-To: AANLkTim0tu2Orb+Rz4Pc9xG5vNMhBWyrTnbNhxvsyN6H@mail.gmail.com
On Sat, 26 Mar 2011 23:08:45 -0500 Ben Key <bkey76@gmail.com> wrote:
BK> Has anyone else started working on this? My business trip lasted a week
BK> longer than expected and I just got home today. I can start working on this
BK> tomorrow if no one else has.
No, I believe you're the only one helping on this. Thank you.
Ted
next prev parent reply other threads:[~2011-03-27 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 4:24 auth-source.el request: NS port needs Mac OS X keychain functions Ben Key
2011-03-14 19:17 ` Ted Zlatanov
2011-03-27 4:08 ` Ben Key
2011-03-27 14:14 ` Ted Zlatanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-12 0:06 Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4fk8xbo.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).