From: Ted Zlatanov <tzz@lifelogs.com>
To: <ding@gnus.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus VCS issues
Date: Wed, 20 Jan 2010 09:05:19 -0600 [thread overview]
Message-ID: <87pr54akb4.fsf@lifelogs.com> (raw)
In-Reply-To: <m3636x7nvd.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 19 Jan 2010 23:04:22 +0100")
On Tue, 19 Jan 2010 23:04:22 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Would it make sense at this point to migrate Gnus out of CVS?
>>
>> Whether we use Subversion or Git or Bazaar, let's use something more
>> reasonable. It would make sync with Emacs, branching, tagging, and
>> releasing simpler. A DVCS is IMHO the best choice today and I would
>> support either Git or Bazaar.
>>
>> We could still host it on gnus.org, of course, and the old CVS server
>> could be available as a read-only mirror. But it could live on Savannah
>> as well.
LMI> I don't really know how much time I could promise to spend on doing
LMI> something like that...
If you're too busy, maybe you'll agree to move the Gnus repo to Savannah
(using Bazaar there). Then gnus.org can simply point to the Savannah
page for checkouts, tarballs, and the web pages (which can also host the
manual snapshots). So from your side it's a one-time effort to migrate
CVS and set up the website links; I think Reiner and I (if Reiner
agrees to this plan) can handle the rest.
Ted
next prev parent reply other threads:[~2010-01-20 15:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 23:35 pop3.el: Display the size of the message being fetched (POP3 LIST command) Bojan Petrovic
2009-02-09 20:11 ` Ted Zlatanov
2009-02-09 22:48 ` Reiner Steib
2009-02-09 23:07 ` Katsumi Yamaoka
2009-02-09 23:38 ` Bojan Petrovic
2009-02-10 14:44 ` Ted Zlatanov
2009-02-10 22:18 ` Reiner Steib
2009-02-11 1:08 ` Bojan Petrovic
2009-04-01 21:21 ` Bojan Petrovic
2009-04-13 15:54 ` Ted Zlatanov
2009-04-16 19:06 ` Reiner Steib
2009-04-16 20:08 ` Ted Zlatanov
2009-08-04 14:32 ` Ted Zlatanov
2009-12-25 20:07 ` Bojan Petrovic
2010-01-05 19:40 ` Ted Zlatanov
2010-01-12 17:16 ` Reiner Steib
2010-01-13 21:13 ` Gnus VCS issues (was: pop3.el: Display the size of the message being fetched (POP3 LIST command)) Ted Zlatanov
2010-01-14 16:40 ` Gnus VCS issues Bojan Nikolic
2010-01-14 19:49 ` Reiner Steib
2010-01-19 22:04 ` Lars Magne Ingebrigtsen
2010-01-20 15:05 ` Ted Zlatanov [this message]
2010-01-20 21:48 ` Andreas Schwab
2010-01-20 22:19 ` Adam Sjøgren
2010-01-20 22:36 ` Reiner Steib
2010-01-20 23:31 ` Adam Sjøgren
2010-01-22 7:11 ` Christian
2010-01-22 16:39 ` Adam Sjøgren
2010-01-25 6:15 ` Miles Bader
2010-01-28 19:16 ` Florian Weimer
2010-01-29 18:39 ` Ted Zlatanov
2010-02-22 20:49 ` Ted Zlatanov
[not found] ` <m3mxytge3r.fsf@quimbies.gnus.org>
2010-03-01 14:28 ` Ted Zlatanov
2010-03-22 13:08 ` Ted Zlatanov
2010-02-01 22:56 ` Byung-Hee HWANG
2010-02-22 21:56 ` Didier Verna
2010-01-20 23:17 ` Andreas Schwab
2010-01-25 6:16 ` Miles Bader
2010-01-20 23:51 ` David Engster
2010-01-21 0:11 ` Adam Sjøgren
2010-01-25 6:20 ` Miles Bader
2010-01-25 11:10 ` David Engster
2010-01-25 13:27 ` Andreas Schwab
2010-03-20 15:21 ` pop3.el: Display the size of the message being fetched (POP3 LIST command) 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=87pr54akb4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=larsi@gnus.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).