unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Subject: Re: gratuitous changes
Date: Sat, 01 Feb 2003 10:54:21 +0100	[thread overview]
Message-ID: <20030201104649.CF7C.LEKTU@terra.es> (raw)
In-Reply-To: <200302010000.h1100nF29021@rum.cs.yale.edu>


On Fri, 31 Jan 2003 19:00:49 -0500
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:

> If we all agree to set things up this way, it's fine.

Well, I think we should agree to maintaing Emacs code in a normalized
way, so these kinds of conflicts (both CVS-wise and people-wise :) get
minimized.

> These were not my trailing whitespaces, but the ones that were in
> the file to start with and that you removed in a large scale, thus
> introducing conflicts in code that you probably didn't even look at.

It was on a large scale only because I checked in the Cygwin patch,
that's large. I, and others, have been commiting changes with trailing
whitespace deleted for months. 

> I don't understand what you're getting at here.

I'm not trying to get anywhere, neither I'm trying to flame or be flamed
at.  I just was expressing my view that we should settle for doing
things the same way (even if it's not my way, yes, but in the issue of
trailing whitespace, seems like the simpler answer, long term).  Sorry
if it came across as angry or whatever.

> Note that there is in my mind a significant difference between
> purely spuriuous whitespace and whitespace which will naturally be
> re-introduced by editing (such as whitespace-only lines which will be
> reintroduced by the next TAB).

There's no such difference in my mind. I have set an underlined face for
the trailing whitespace so I do see it immediately. If I edit something
and accidentally introduce the whitespace, I promptly delete it.

> I'm not necessarily opposed to stripping all whitespace-only
> line, but then let's do it once and for all in a single commit
> so even though it will fuck up `cvs diff' output, I will
> at least know how I can trivially resolve all the conflicts.

I can agree with that.

> 	Stefan "about 200 locally modified files"

Ouch :)

(Summary of my message: I'm really sorry for bringing trouble to you;
but I'd like to fix the "problem" as easily and painlessly as posible.)

-- 
Juanma Barranquero <lektu@terra.es>

  parent reply	other threads:[~2003-02-01  9:54 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 21:48 gratuitous changes Stefan Monnier
2003-01-31 22:16 ` Andreas Schwab
2003-01-31 22:51   ` John Wiegley
2003-01-31 23:01 ` Juanma Barranquero
2003-02-01  0:00   ` Stefan Monnier
2003-02-01  6:51     ` Robert Anderson
2003-02-03 15:09       ` Stefan Monnier
2003-02-03 16:20         ` Robert Anderson
2003-02-01  9:54     ` Juanma Barranquero [this message]
2003-02-01  2:11 ` Miles Bader
2003-02-01 18:44   ` Bill Wohler
2003-02-01 22:11 ` Richard Stallman
2003-02-01 23:28   ` Martin Stjernholm
2003-02-02  5:52     ` Eli Zaretskii
2003-02-02  6:14       ` Miles Bader
2003-02-06 16:34         ` Martin Stjernholm
2003-02-06 17:22           ` Miles Bader
2003-02-10  0:29             ` Martin Stjernholm
2003-02-03 14:57     ` Stefan Monnier
2003-02-02  5:56 ` Eli Zaretskii
2003-02-02 12:56   ` Juanma Barranquero
2003-02-02 13:59   ` Kim F. Storm
2003-02-03 13:01     ` Richard Stallman
2003-02-03 14:11       ` Juanma Barranquero
2003-02-03 14:54         ` Stefan Monnier
2003-02-03 15:01           ` Juanma Barranquero
2003-02-04 14:59       ` Juanma Barranquero
2003-02-04 16:09         ` Robert Anderson
2003-02-04 16:44           ` Juanma Barranquero
2003-02-04 17:14             ` Robert Anderson
2003-02-04 17:22               ` Juanma Barranquero
2003-02-04 19:46         ` Eli Zaretskii
2003-02-04 20:16           ` Juanma Barranquero
2003-02-04 20:22             ` Stefan Monnier
2003-02-04 20:44               ` Nick Roberts
2003-02-04 22:59                 ` Edward O'Connor
2003-02-04 23:19                   ` Juanma Barranquero
2003-02-05  0:32                   ` Kim F. Storm
2003-02-05  0:39                     ` Kim F. Storm
2003-02-05  0:49                       ` Kenichi Handa
2003-02-05  4:24                     ` Luc Teirlinck
2003-02-05  4:51                       ` Miles Bader
2003-02-06  2:42                   ` Richard Stallman
2003-02-06  4:09                     ` Luc Teirlinck
2003-02-07  9:18                       ` Richard Stallman
2003-02-04 23:18                 ` Juanma Barranquero
2003-02-05  0:42                   ` Stefan Monnier
2003-02-05  6:03                 ` Eli Zaretskii
2003-02-06  2:42                 ` Richard Stallman
2003-02-06  2:54                   ` Luc Teirlinck
2003-02-04 23:14               ` Juanma Barranquero
2003-02-05  6:01             ` Eli Zaretskii
2003-02-05  8:18               ` Juanma Barranquero
2003-02-05 15:30                 ` Eli Zaretskii
2003-02-14 22:56                   ` Thien-Thi Nguyen
2003-02-05  0:14         ` Richard Stallman
2003-02-07 14:02 ` Francesco Potorti`
2003-02-10  1:47   ` Miles Bader
2003-02-10 10:09     ` Francesco Potorti`

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=20030201104649.CF7C.LEKTU@terra.es \
    --to=lektu@terra.es \
    /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).