all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: emacs-devel@gnu.org
Subject: Re: Lack of tooling slowing down contributions
Date: Fri, 14 Jun 2019 10:58:25 +0300	[thread overview]
Message-ID: <83h88sy4wu.fsf@gnu.org> (raw)
In-Reply-To: <87ftocy5uv.fsf@cassou.me> (message from Damien Cassou on Fri, 14 Jun 2019 09:38:00 +0200)

> From: Damien Cassou <damien@cassou.me>
> Date: Fri, 14 Jun 2019 09:38:00 +0200
> 
> I've submitted several patches to Emacs.  Because I don't do it very
> often, I tend to forget the details in CONTRIBUTE.  Because I'm lazy,
> I'm not reading CONTRIBUTE before each new contribution.  As a result,
> my patches are not good enough and reviewers have to spend time telling
> me how to do things.  I don't think reviewers should spend their
> valuable time checking for details that can be checked by a machine.
> 
> These checks could be done either (by order of preference):

I suggest to file a feature-request bug report with these proposals.

Thanks.



  reply	other threads:[~2019-06-14  7:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  7:38 Lack of tooling slowing down contributions Damien Cassou
2019-06-14  7:58 ` Eli Zaretskii [this message]
2019-06-14 11:19 ` Noam Postavsky
2019-06-16 19:20   ` Juri Linkov
2019-06-16 22:44     ` Stefan Monnier
2019-06-17 21:08       ` Juri Linkov
2019-06-16 23:06     ` Phil Sainty
2019-06-17  5:44       ` Van L
2019-06-17  9:53       ` Marcin Borkowski
2019-06-17 10:22         ` Yuri Khan
2019-06-17 21:19       ` Juri Linkov
2019-06-18 21:29         ` Juri Linkov
2019-06-19 12:50           ` Andy Moreton
2019-06-19 20:47             ` Juri Linkov
2019-06-19 21:26               ` Noam Postavsky
2019-06-17  6:57     ` Damien Cassou

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=83h88sy4wu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=damien@cassou.me \
    --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.