From: Erik Colson <eco@ecocode.net>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: emacs repo and gnus repo
Date: Fri, 27 Jul 2012 00:37:40 +0200 [thread overview]
Message-ID: <m2k3xqtah7.fsf@ecocode.net> (raw)
In-Reply-To: <b4mwr1qw416.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 27 Jul 2012 07:28:37 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Erik Colson wrote:
>> I'm used to compile Emacs from the bzr repo, and then get gnus from its
>> own repo. However gnus is already present in the emacs bzr repo. So,
>> maybe I don't need to get gnus from it's own repo... How close is emacs
>> gnus repo from gnus repo ?
>
> I'm a merging engineer; Gnus is being synchronized between Emacs
> bzr trunk and Gnus git master day after day except for some IMAP
> related functions:
>
> http://article.gmane.org/gmane.emacs.devel/149948
>
> So, you may want to install Ma Gnus from the git repo if you'd
> like to try those ambitions. The differences between bzr and git
> are in:
>
> ftp://ftp.jpl.org/pub/tmp/MaGnus-to-Emacs.patch
Thanks for the information. I figure I'll continue using gnus from the
git repo then.
Thanks
--
erik
prev parent reply other threads:[~2012-07-26 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 12:02 Erik Colson
2012-07-26 22:28 ` Katsumi Yamaoka
2012-07-26 22:37 ` Erik Colson [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=m2k3xqtah7.fsf@ecocode.net \
--to=eco@ecocode.net \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).