unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: bruce.connor.am@gmail.com
Cc: Eli Zaretskii <eliz@gnu.org>,
	Lars Magne Ingebrigtsen <larsi@gnus.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Emacs author stats
Date: Fri, 24 Apr 2015 10:43:00 +0900	[thread overview]
Message-ID: <87zj5yqp23.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CAAdUY-KJRL3j1Ne3Zmr1MRRV1p6oX8=WdxvkzUK8MW0opLqiFQ@mail.gmail.com>

Artur Malabarba writes:

 > Either way, I think the relevant metric is precisely the number of
 > *committers*. Commiters are the ones most affected by this change.
 > Authors who submit patches and bug fixes couldn't care less whether we
 > use bzr or git (or do I misunderstand something?).

Back when "bzr branch" from Savannah sometimes took several hours or
didn't finish at all, I'm sure that some potential authors found that
plus the request to verify bugs and patch compatibility with trunk
HEAD made it worth their while to remain potential.

And as Eli says, it's authors that matter to the volume of
contributions.




  parent reply	other threads:[~2015-04-24  1:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 17:41 Emacs author stats Lars Magne Ingebrigtsen
2015-04-23 17:49 ` Eli Zaretskii
2015-04-23 18:27   ` John Wiegley
2015-04-23 18:44   ` Lars Magne Ingebrigtsen
2015-04-23 19:54     ` Eli Zaretskii
2015-04-23 18:48   ` Artur Malabarba
2015-04-23 19:05     ` Lars Magne Ingebrigtsen
2015-04-23 19:55     ` Eli Zaretskii
2015-04-23 19:59       ` Dmitry Gutov
2015-04-23 20:10         ` Eli Zaretskii
2015-04-23 22:33           ` Artur Malabarba
2015-04-24  8:46           ` Peder O. Klingenberg
2015-04-24 13:55       ` Stefan Monnier
2015-04-23 20:01     ` chad
2015-04-24  1:43     ` Stephen J. Turnbull [this message]
2015-04-23 18:49 ` Artur Malabarba

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zj5yqp23.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).