Split mu4e into its own repo

[monsanto]

This would be easy to do if mu was made a github organization. The reasons for this are

1. i'm not interested in non-emacs commits or issues
2. i like to add all of the modules i use as git submodules in an elisp/ directory. This is not as nice to do when the elisp is in a subdirectory, and updates don't necessarily change anything for emacs.

I would probably also mirror mu's C source, but in a different directory.

[djcb]

There's a hard dependency between mu & mu4e, and I don't see that change anytime soon. Often, new mu4e features (or even fixes) depend on changes in the back-end.

So, for the foreseeable future, you'll have to live with the way it works currently...

[the-kenny]

It might be possible to provide an package.el version as soon as both are
matured and mu starts being api compatible with old versions.
Am 29.08.2012 23:35 schrieb "Dirk-Jan C. Binnema" <notifications@github.com

:

There's a hard dependency between mu & mu4e, and I don't see that change
anytime soon. Often, new mu4e features (or even fixes) depend on changes in
the back-end.

So, for the foreseeable future, you'll have to live with the way it works
currently...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-8142059.