From: Kaushal Modi <kaushal.modi@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Trouble merging line-numbers branch into master
Date: Fri, 07 Jul 2017 15:43:24 +0000 [thread overview]
Message-ID: <CAFyQvY0N4UuNfPQW48JgFb8nt_2pFz80u_h_mHATYKiYCg7AqA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]
Hello,
I have having trouble merging the scratch/line-numbers branch into master.
I get one merge conflict in NEWS. That is fine; I resolved that locally.
But then further merging fails because of
1 git … commit --
lisp/progmodes/cc-fonts.el:1251: space before tab in indent.
+ (c-major-mode-is 'c++-mode)
lisp/progmodes/cc-fonts.el:1252: space before tab in indent.
+ (save-excursion (c-back-over-member-initializers)))
You can see that there is white-space trapped between tabs (whitespace
mode) on lines 1251 and 1252:
[image: image.png]
(Look! I am making use of the new line-numbers feature to visually
communicate with people remotely :) )
So something is configured in git that blocks this merging is such mix of
white-space/tabs is seen? In any case, I removed those spaces, but still
cannot proceed with the merge. How can I move forward with the merge?
Also, shouldn't that commit have been blocked in the first place instead of
complaining about it when merging?
--
Kaushal Modi
[-- Attachment #1.2: Type: text/html, Size: 1677 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 35535 bytes --]
next reply other threads:[~2017-07-07 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 15:43 Kaushal Modi [this message]
2017-07-07 15:51 ` Trouble merging line-numbers branch into master 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
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=CAFyQvY0N4UuNfPQW48JgFb8nt_2pFz80u_h_mHATYKiYCg7AqA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--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.