From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] diff.c: Fix whitespace issues due to a mismerge(?)
Date: Tue, 09 May 2017 11:06:50 +0900 [thread overview]
Message-ID: <xmqqo9v26ax1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170508184354.31671-1-sbeller@google.com> (Stefan Beller's message of "Mon, 8 May 2017 11:43:54 -0700")
Stefan Beller <sbeller@google.com> writes:
> It looks like all these lines were introduced by one of the conflict chunks
> in 4af9a7d344 (Merge branch 'bc/object-id', 2016-09-19). Viewing that
> commit in gitk, the indentation seems fine, i.e. there is just one
> whitespace in front of the lines, as you would expect from a formatted
> patch.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>
> Junio,
> I do not think it is worth to apply this patch on its own,
> but maybe it is worth to investigate your setup? (Assuming it is
> git that did the merge, we may have a bug in whitespacing and
> merge conflicts.)
Thanks for spotting.
I do not think you have to worry about any bug in Git-the-program
with this merge. If you try to reproduce the merge yourself (which
by the way is easy to do, with "M=4af9a7d344 && git checkout $M^ &&
git merge $M^2"), you'll see that quite a lot of changes made to
"builtin/apply.c" had to be hand-ported to the corresponding lines
that are now in "apply.c" at the top-level, because in the meantime
13b5af22 ("apply: move libified code from builtin/apply.c to
apply.{c,h}", 2016-04-22) moved things around while the merged side
branch has been cooking.
It is very likely that manual killing and yanking in Emacs
introduced the screw-up.
next prev parent reply other threads:[~2017-05-09 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 18:43 [PATCH] diff.c: Fix whitespace issues due to a mismerge(?) Stefan Beller
2017-05-09 2:06 ` Junio C Hamano [this message]
2017-05-09 2:38 ` Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo9v26ax1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/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://80x24.org/mirrors/git.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).