all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Alan Mackenzie <acm@muc.de>,
	Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Trouble merging line-numbers branch into master
Date: Fri, 07 Jul 2017 21:46:44 +0000	[thread overview]
Message-ID: <CAFyQvY3-JTfX_O=uFKhr=ws2MC58xM-48NwiXTn8QODZ+abC-A@mail.gmail.com> (raw)
In-Reply-To: <95b91e6b-c53e-c969-cda1-998803d301cc@cs.ucla.edu>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Fri, Jul 7, 2017 at 5:41 PM Paul Eggert <eggert@cs.ucla.edu> wrote:

> Presumably the lines in question were changed in one branch or the other
> (not
> necessarily by messing with white space), and our git settings are
> suggesting
> that you omit the spaces before tabs while you're futzing with those lines.
>
> As build-aux/git-hooks/pre-commit suggests, you can work around the problem
> temporarily with the shell command 'git config core.whitespace
> -trailing-space'.
> I don't recommend this setting in general, though.
>

I found the error useful. So when line-numbers branch is eventually merged,
instead of ignoring/bypassing this error, I'd suggest that that
tab+space+tab combo be fixed and that whole thing be made to contain only
tabs or only spaces (my preference).

Slowly and gradually, as more merges and commits happen in future, all such
mixtures of tabs+spaces will get removed.
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1352 bytes --]

  reply	other threads:[~2017-07-07 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 15:43 Trouble merging line-numbers branch into master Kaushal Modi
2017-07-07 15:51 ` Noam Postavsky
2017-07-07 18:08   ` Kaushal Modi
2017-07-07 21:23 ` Alan Mackenzie
2017-07-07 21:38   ` Stefan Monnier
2017-07-07 21:41   ` Paul Eggert
2017-07-07 21:46     ` Kaushal Modi [this message]
2017-07-08  8:04       ` Eli Zaretskii
2017-07-08 12:05         ` Noam Postavsky
2017-07-08 12:46           ` Kaushal Modi

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='CAFyQvY3-JTfX_O=uFKhr=ws2MC58xM-48NwiXTn8QODZ+abC-A@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=acm@muc.de \
    --cc=eggert@cs.ucla.edu \
    --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.