From: Sean Sieger <sean.sieger@gmail.com>
To: emacs-devel@gnu.org
Cc: bbdb-info@lists.sourceforge.net
Subject: Re: bbdb
Date: Fri, 15 Nov 2013 10:35:21 -0500 [thread overview]
Message-ID: <87r4ahoeyu.fsf@gmail.com> (raw)
In-Reply-To: jwvob5l3cxc.fsf-monnier+emacs@gnu.org
> It's the other way around: the copyright needs to be sorted out in order
> to be able to move BBDB into GNU ELPA.
Of course. :[
prev parent reply other threads:[~2013-11-15 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 19:42 bbdb Sean Sieger
2013-11-10 23:29 ` bbdb Roland Winkler
2013-11-11 2:07 ` bbdb Stefan Monnier
2013-11-11 15:49 ` bbdb Ted Zlatanov
2013-11-12 7:54 ` bbdb Richard Stallman
2013-11-11 22:46 ` bbdb Richard Stallman
2013-11-15 14:26 ` bbdb Sean Sieger
2013-11-15 15:25 ` bbdb Stefan Monnier
2013-11-15 15:35 ` Sean Sieger [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
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=87r4ahoeyu.fsf@gmail.com \
--to=sean.sieger@gmail.com \
--cc=bbdb-info@lists.sourceforge.net \
--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).