all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] trunk r117000: Untabify cl-macs.el
Date: Mon, 21 Apr 2014 14:03:27 +0200	[thread overview]
Message-ID: <CAAeL0SRPy_M-2p9MBHbSCcnr437cPFpS47iNmDYXcAJDu-hVxA@mail.gmail.com> (raw)
In-Reply-To: <5354D99B.5090101@dancol.org>

On Mon, Apr 21, 2014 at 10:40 AM, Daniel Colascione <dancol@dancol.org> wrote:

> No, we can only control what code gets into Emacs.

Even so, is not for you alone to decide what goes or doesn't go into
the Emacs repo. This is a long standing issue, and the consensus is,
more or less, that you do what you want with the code you write, and
you try not to change it gratuitously in other code you fix (so, not
(un)?tabifying an entire file just because you commit a fix to it).
Anything else is bound to cause much discussion and grief.

(I prefer untabified code, BTW.)

    J



  parent reply	other threads:[~2014-04-21 12:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Wc1iD-0005Z5-Tb@vcs.savannah.gnu.org>
2014-04-21  0:28 ` [Emacs-diffs] trunk r117000: Untabify cl-macs.el Daniel Colascione
2014-04-21  7:10   ` Eli Zaretskii
2014-04-21  7:13     ` Daniel Colascione
2014-04-21  8:03       ` Stephen J. Turnbull
2014-04-21  8:38       ` Eli Zaretskii
2014-04-21  8:40         ` Daniel Colascione
2014-04-21  8:48           ` Eli Zaretskii
2014-04-21 12:03           ` Juanma Barranquero [this message]
2014-04-21 16:28       ` Lars Magne Ingebrigtsen
2014-04-21 18:17       ` Josh
2014-04-21 18:22         ` Daniel Colascione
2014-04-21 21:27         ` Stefan Monnier
2014-04-21 12:49   ` Stefan Monnier

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=CAAeL0SRPy_M-2p9MBHbSCcnr437cPFpS47iNmDYXcAJDu-hVxA@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=dancol@dancol.org \
    --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.