all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Avoiding the three-windows merging with Git
Date: Mon, 25 Nov 2019 22:46:47 -0500	[thread overview]
Message-ID: <E1iZRoN-0000cW-RE@fencepost.gnu.org> (raw)
In-Reply-To: <83sgmcskaw.fsf@gnu.org> (message from Eli Zaretskii on Mon, 25 Nov 2019 05:32:07 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > Has anyone figured out why merge conflicts go into a mode
  > > with three windows, and some way to turn that off
  > > without breaking anything else?

  > No.  The only idea was that you somehow inadvertently started Ediff.
  > That shouldn't be necessary, and doesn't happen automatically, so it's
  > unclear how it happened, if it did.

I never use it, so unless I started it by typo, I don't think I started it.
And ISTR it happened more than once.

I don't know how to provoke a conflict intentionally.
I'd have to ask someone to install a patch that conflicts
with something I want to install.  However, doing that in
a Git repo where it will be impossible to remove later
seems like a bad idea.

Can someone help me create a conflict to test handling it?

-- 
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2019-11-26  3:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25  3:14 Avoiding the three-windows merging with Git Richard Stallman
2019-11-25  3:32 ` Eli Zaretskii
2019-11-26  3:46   ` Richard Stallman [this message]
2019-11-26  7:16     ` Kévin Le Gouguec
2019-11-27  6:45       ` Richard Stallman
2019-11-27  9:39         ` Marcin Borkowski
2019-11-27 20:15           ` Kévin Le Gouguec
2019-11-27 22:48             ` Marcin Borkowski
2019-11-28  4:17           ` Richard Stallman
2019-11-27 15:45         ` Eli Zaretskii
2019-11-27 19:45           ` Kévin Le Gouguec

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=E1iZRoN-0000cW-RE@fencepost.gnu.org \
    --to=rms@gnu.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.