From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org, emacs-devel@gnu.org
Subject: Gnus Git synchronization with Emacs Bazaar (was: The Gnus repository is switching to Git as of 2010-04-19)
Date: Wed, 21 Apr 2010 06:03:56 -0500 [thread overview]
Message-ID: <874oj5m5ib.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <jwv633lqz2m.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 20 Apr 2010 23:16:30 -0400")
On Tue, 20 Apr 2010 23:16:30 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Assuming this rename tracking works well, new files will be managed by
>> the Gnus synchronization maintainer. The Emacs side should be
>> authoritative for new files, meaning that we (Gnus) will get lisp/new.el
>> and have to remove it, and that we will push our lisp/gnus-new.el to
>> your lisp/gnus/gnus-new.el.
SM> Hopefully Git can also figure out where to put new files. But if not,
SM> I really can't imagine why you'd insist on doing it "all on the Git
SM> side".
To avoid working on the Bazaar side.
>> what other branches do we need immediately?
SM> We have the `emacs-23' branch which should sync with the "stable" branch
SM> of Gnus (not sure which one that is because I don't track Gnus
SM> development closely enough).
Reiner should decide this since he's been doing branches and tags in CVS
so far, but it probably makes sense to call our branch "emacs-23" as
well. The branch name may be confusing because of the "emacs_23_1_RC"
branch we inherited from CVS, but with Emacs 24 and later the scheme
will work.
On Wed, 21 Apr 2010 12:31:03 +0900 "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
SJT> *What I would do if I were you* is lobby for a new subtree, "packages",
SJT> of the Emacs tree, and just plop Gnus into that, with its Lisp and
SJT> support files all under packages/gnus. Add a make rule which puts
SJT> appropriate Gnus autoloads into the loaddefs or whatever Emacs uses,
SJT> to find Gnus' Lisp and data in there. (Directory symlinks would work,
SJT> as in XEmacs' "symlink farm installation" option, but aren't
SJT> acceptable as long as systems that can't symlink easily are
SJT> supported.)
I was planning to make Gnus one of the first package.el packages under
Emacs; we've discussed a separate "trusted FSF packages" repository
which will be better than the subtree you suggest. Installing Gnus
through package.el will DTRT regardless.
But that doesn't eliminate the synchronization problem: we still want to
keep the current setup and let Emacs keep its own version of some Gnus
files like message.el. Only lisp/gnus/*.el, some docs, and some images
will move to the Gnus package.
SJT> The way you're going, you're just making the same mistake XEmacs
SJT> made with its package system (having the installed tree look
SJT> different from the source tree), except that you're going to have
SJT> more pain than we do because of the possibility of shooting off
SJT> both your feet.
I think that Gnus is a special case and we shouldn't adapt Emacs'
packaging system to accomodate it.
Thanks
Ted
next prev parent reply other threads:[~2010-04-21 11:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 17:34 The Gnus repository is switching to Git as of 2010-04-19 Ted Zlatanov
2010-04-19 18:21 ` Sivaram Neelakantan
2010-04-19 19:13 ` Ted Zlatanov
2010-04-21 8:50 ` Steinar Bang
2010-04-21 9:01 ` David Engster
2010-04-21 9:02 ` David Engster
2010-04-21 10:05 ` Andreas Schwab
2010-04-21 12:12 ` Andreas Schwab
2010-04-21 14:10 ` Ted Zlatanov
2010-04-21 14:54 ` Andreas Schwab
2010-04-23 0:55 ` Ted Zlatanov
2010-04-22 8:12 ` Steinar Bang
2010-04-19 19:17 ` Sven Joachim
2010-04-20 13:03 ` Harry Putnam
2010-04-20 13:29 ` Ted Zlatanov
2010-04-20 13:57 ` Andreas Schwab
[not found] ` <jwvr5mb8evr.fsf-monnier+emacs@gnu.org>
2010-04-20 13:55 ` Ted Zlatanov
2010-04-20 15:00 ` Stefan Monnier
2010-04-20 20:05 ` Ted Zlatanov
2010-04-20 22:28 ` Stefan Monnier
2010-04-20 23:44 ` Ted Zlatanov
2010-04-21 3:16 ` Stefan Monnier
2010-04-21 11:03 ` Ted Zlatanov [this message]
2010-04-22 2:24 ` Gnus Git synchronization with Emacs Bazaar (was: The Gnus repository is switching to Git as of 2010-04-19) Stephen J. Turnbull
2010-04-21 0:33 ` The Gnus repository is switching to Git as of 2010-04-19 Stephen J. Turnbull
2010-04-21 0:51 ` Ted Zlatanov
2010-04-21 3:31 ` Stephen J. Turnbull
2010-04-21 3:11 ` Stefan Monnier
2010-04-21 4:00 ` Stephen J. Turnbull
2010-04-21 9:01 ` Andreas Schwab
2010-04-21 2:59 ` Teemu Likonen
2010-04-21 11:30 ` Ævar Arnfjörð Bjarmason
2010-04-21 14:57 ` Teemu Likonen
2010-04-21 16:36 ` Ævar Arnfjörð Bjarmason
2010-04-23 1:09 ` cgit beautification (was: The Gnus repository is switching to Git as of 2010-04-19) Ted Zlatanov
2011-02-25 22:04 ` cgit beautification Ted Zlatanov
2011-02-25 22:56 ` Adam Sjøgren
2011-02-25 23:19 ` Adam Sjøgren
2011-02-26 12:05 ` Lars Ingebrigtsen
2011-03-01 10:27 ` Ted Zlatanov
2011-03-01 10:30 ` Ted Zlatanov
2011-03-01 11:31 ` Adam Sjøgren
2011-03-01 13:32 ` Ted Zlatanov
2011-03-01 17:08 ` Adam Sjøgren
2011-03-02 11:05 ` Ted Zlatanov
2010-04-22 5:49 ` The Gnus repository is switching to Git as of 2010-04-19 Harry Putnam
2010-04-23 0:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874oj5m5ib.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--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.
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).