From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: git/hg Gnus repository
Date: Mon, 06 Jul 2009 11:46:43 +0200 [thread overview]
Message-ID: <m21voum9do.fsf@gwdg-mac-engster.top.gwdg.de> (raw)
In-Reply-To: <87iqi6pxcs.fsf@catnip.gol.com> (Miles Bader's message of "Mon, 06 Jul 2009 07:40:35 +0900")
Miles Bader <miles@gnu.org> writes:
> David Engster <deng@randomsample.de> writes:
>> I would also like to look at bzr, since this is what Emacs is going to
>> use.
>
> It's definitely a point to consider, but my impression is that almost
> nobody except rms (amongst the emacs devs) actually seems to like bzr...
Yes, I've followed the discussion on emacs-devel. Compared to Emacs,
Gnus is a much smaller project though, so I reckon the much discussed
performance problem regarding 'bzr log' et al. wouldn't be such a big
issue. I just thought that using bzr for Gnus would make syncing with
Emacs easier, but I guess converting from git or hg wouldn't be a big
deal, either.
I personally use (and prefer) git, but at the moment I would already be
happy if Gnus would switch to any DVCS at all.
-David
next prev parent reply other threads:[~2009-07-06 9:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 11:57 David Engster
2008-12-13 15:10 ` Reiner Steib
2008-12-13 15:35 ` David Engster
2009-08-15 8:01 ` Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed (was: git/hg Gnus repository) Reiner Steib
2009-08-15 8:25 ` Gnus repositories - corruption of gnus-uu.el and gnus-xmas.el fixed David Engster
2009-08-29 10:10 ` Adam Sjøgren
2008-12-14 16:53 ` git/hg Gnus repository Kalle Olavi Niemitalo
2008-12-14 22:10 ` David Engster
2008-12-15 22:30 ` David Engster
2009-02-14 21:44 ` Eric Schulte
2009-02-15 16:18 ` David Engster
2009-02-15 18:09 ` Eric Schulte
2009-06-30 8:13 ` Andreas Seltenreich
2009-06-30 8:28 ` David Engster
2009-07-05 22:40 ` Miles Bader
2009-07-06 9:46 ` David Engster [this message]
2009-07-08 18:58 ` 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=m21voum9do.fsf@gwdg-mac-engster.top.gwdg.de \
--to=deng@randomsample.de \
--cc=ding@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).