From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: patch vs. overwrite in bzr
Date: Wed, 04 Apr 2012 21:38:39 +0200 [thread overview]
Message-ID: <87wr5v5lts.fsf@gmail.com> (raw)
In-Reply-To: <83bon7co4j.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Apr 2012 22:07:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Wed, 04 Apr 2012 19:53:53 +0200
>>
>> You should not have to overview the dev branch, only the trunk and merge
>> regularly it in the dev branch. You would have only to review the
>> patches before applying to dev branch, but that's what you already do I
>> think. The difference is just that actually you say, yes patch is ok we
>> will apply it after feature freeze. Instead you would just have to apply
>> if ok.
>
> Not true. There's a difference between doing a triage and actually
> considering the patch for inclusion. In addition, "overviewing" means
> discussing design and implementation for significant contributions.
> Development is not just patch reviews, at least not in Emacs.
You are already doing this, so it is not extra work.
>> >> I think Emacs lost a lot a new features during this process, especially
>> >> from contributors that send patches; most patches are lost or
>> >> are unusable after several months of modifications in trunk.
>> >
>> > If you use bzr or any other dVCS, you can simply put your changes on a
>> > branch or even a shelf, and then when the time comes to push them, you
>> > will have much less trouble than you think. Modern VCSes do a very
>> > good job at merging.
>> I know this, I use patches that I can pop and push again after pulling
>> last changes upstream.
>
> Then why do you present patch-rot as a significant factor?
Most people don't want to do this and just do not contribute, so you
lose many potentials contributors.
> It isn't.
It is actually not easy to contribute to Emacs.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2012-04-04 19:38 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 13:28 Next pretest, and regressions policy Chong Yidong
2012-03-31 10:15 ` Bastien
2012-04-01 9:55 ` Bastien
2012-04-01 12:37 ` =?utf-8?Q?=C3=93scar_Fuentes?=
2012-04-01 13:30 ` Stefan Monnier
2012-04-01 17:09 ` Chong Yidong
2012-04-01 20:32 ` Bastien
2012-04-02 4:12 ` Chong Yidong
2012-04-01 20:32 ` Bastien
2012-04-03 8:20 ` patch vs. overwrite in bzr [was: Next pretest, and regressions policy] Roland Winkler
2012-04-03 12:36 ` Óscar Fuentes
2012-04-03 13:42 ` Bastien
2012-04-03 15:02 ` patch vs. overwrite in bzr =?utf-8?Q?=C3=93scar_Fuentes?=
2012-04-03 15:03 ` David Engster
2012-04-03 16:31 ` Stefan Monnier
2012-04-03 17:40 ` Michael Albinus
2012-04-03 15:32 ` patch vs. overwrite in bzr [was: Next pretest, and regressions policy] Stefan Monnier
2012-04-03 16:52 ` patch vs. overwrite in bzr Glenn Morris
2012-04-03 20:50 ` Bastien
2012-04-03 21:27 ` Glenn Morris
2012-04-04 0:26 ` Stefan Monnier
2012-04-04 5:45 ` Bastien
2012-04-04 5:51 ` Bastien
2012-04-04 6:46 ` Michael Albinus
2012-04-04 8:35 ` Thierry Volpiatto
2012-04-04 13:20 ` Stefan Monnier
2012-04-04 16:39 ` Jordi Gutiérrez Hermoso
2012-04-04 16:52 ` Paul Eggert
2012-04-04 17:09 ` Eli Zaretskii
2012-04-04 17:53 ` Thierry Volpiatto
2012-04-04 19:07 ` Eli Zaretskii
2012-04-04 19:38 ` Thierry Volpiatto [this message]
2012-04-04 20:12 ` Eli Zaretskii
2012-04-04 13:16 ` Stefan Monnier
2012-04-04 17:01 ` Eli Zaretskii
2012-04-04 18:07 ` Stefan Monnier
2012-04-04 19:11 ` Eli Zaretskii
2012-04-04 20:11 ` David Engster
2012-04-04 22:06 ` Stefan Monnier
2012-04-05 3:09 ` Eli Zaretskii
2012-04-05 13:22 ` Stefan Monnier
2012-04-05 15:24 ` Lars Magne Ingebrigtsen
2012-04-05 15:57 ` Eli Zaretskii
2012-04-05 17:10 ` Ted Zlatanov
2012-04-06 7:13 ` Richard Stallman
2012-04-06 8:29 ` Bastien
2012-04-06 8:40 ` Eli Zaretskii
2012-04-06 9:20 ` Bastien
2012-04-06 9:57 ` Eli Zaretskii
2012-04-06 10:20 ` Bastien
2012-04-06 17:26 ` chad
2012-04-06 20:01 ` joakim
2012-04-06 20:52 ` Eli Zaretskii
2012-04-07 2:28 ` Óscar Fuentes
2012-04-07 6:33 ` Eli Zaretskii
2012-04-07 11:56 ` Óscar Fuentes
2012-04-07 12:10 ` Eli Zaretskii
2012-04-07 12:56 ` Óscar Fuentes
2012-04-07 13:32 ` Eli Zaretskii
2012-04-07 13:42 ` Óscar Fuentes
2012-04-07 7:07 ` Andreas Schwab
2012-04-07 11:44 ` Óscar Fuentes
2012-04-06 21:10 ` Juanma Barranquero
2012-04-16 10:45 ` Jason Rumney
2012-04-16 16:38 ` Eli Zaretskii
2012-04-06 16:17 ` Christophe Poncy
2012-04-06 16:41 ` Eli Zaretskii
2012-04-06 17:14 ` Christophe Poncy
2012-04-07 0:17 ` Richard Stallman
2012-04-07 0:17 ` Richard Stallman
2012-04-07 9:15 ` Bastien
2012-04-07 22:19 ` Richard Stallman
2012-04-09 9:39 ` Bastien
2012-04-08 3:25 ` Richard Stallman
2012-04-08 15:52 ` Ted Zlatanov
2012-04-16 22:02 ` Richard Stallman
2012-04-06 8:43 ` Eli Zaretskii
2012-04-04 17:12 ` patch vs. overwrite in bzr [was: Next pretest, and regressions policy] Eli Zaretskii
2012-04-05 7:13 ` Bastien
2012-04-05 15:53 ` Eli Zaretskii
2012-04-11 14:36 ` Bastien
2012-04-04 18:01 ` Thierry Volpiatto
2012-04-05 7:19 ` Bastien
2012-04-05 9:16 ` Thierry Volpiatto
2012-04-01 20:35 ` Next pretest, and regressions policy Bastien
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=87wr5v5lts.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.