Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Cc: <reiner.steib@gmx.de>, <ding@gnus.org>
Subject: Re: Gnus VCS issues
Date: Mon, 1 Mar 2010 08:28:56 -0600	[thread overview]
Message-ID: <87sk8kqfo7.fsf@lifelogs.com> (raw)
In-Reply-To: <m3mxytge3r.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 01 Mar 2010 00:00:40 +0100")

On Mon, 01 Mar 2010 00:00:40 +0100 Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org> wrote: 

LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Reiner, Lars, are you for or against switching Gnus to Bazaar?
>> 
>> Note pretty much everyone, me included, is OK with Git instead of
>> Bazaar.  It can be synchronized with Bazaar and interfaces like Magit
>> make it really nice.  So really I'm pushing for a decent DVCS, although
>> I'd prefer Bazaar or Git over the others.

LMI> I'm pretty much agnostic -- I have little experience with either bzr or
LMI> git.  

My experience with Git has been more positive.  A common complaint on
the emacs-devel list is memory issues, where Bazaar baloons to hundreds
of MB, and it uses a *crazy* amount of bandwidth, also hundreds of MB
for a single pull if the commit log requires it.  There's also much more
Git knowledge and nice wrappers out there, so I say let's use Git, at
least for now.  Since there's an existing Git mirror mentioned in this
thread we can simply make a clone of it after review for consistency.

If you haven't used Git, I recommend the Magit Emacs package.  The docs
are great and it simplifies the common tasks (the
update-or-rebase->hack->stage->commit-or-ammend cycle).

>> If yes to Bazaar, are you in favor of hosting with Savannah or keeping
>> it on gnus.org?  I assume with Git it would be hosted on gnus.org.

LMI> I could give somebody (Reiner, for instance?) access to quimby.gnus.org
LMI> to install the server, if that's required.

Either Reiner or I can do it.  We should also review the list of
comitters and change their passwords as a security measure if we're
changing the server anyhow.  You or one of us can make the CVS server
read-only and keep it around, updating from Git.

The Emacs developers need to be aware of this change too so they can
pull deltas into the Emacs tree and push bugfixes back into the Gnus
tree.  I don't expect that change to be a problem.

Reiner, are you all right with this plan?  Would you like to work on
quimby or should I?

Thanks
Ted



  parent reply	other threads:[~2010-03-01 14:28 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
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 [this message]
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=87sk8kqfo7.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=larsi@quimbies.gnus.org \
    --cc=reiner.steib@gmx.de \
    /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).