all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Resuming M-x gitmerge
Date: Mon, 11 Jun 2018 11:50:04 -0400	[thread overview]
Message-ID: <qm36xtjpar.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87h8mayz71.fsf@gmail.com> (Noam Postavsky's message of "Sun, 10 Jun 2018 19:54:58 -0400")

Noam Postavsky wrote:

> When M-x gitmerge hits a conflict, it shows a window with the message:
>
>     Resolve the conflicts manually, then run gitmerge again.
>     Note:
>       - You don't have to add resolved files or commit the merge yourself (but you can).
[...]
> The first note is either wrong, or I'm misunderstanding it.  If I don't
> 'git add' the resolved files and commit the merge, then trying to run
> M-x gitmerge again fails with (user-error "Repository is not clean").

Maybe it's just badly worded? You have to resolve the conflict someway.
This is either by editing the conflicted file and using "git add" to
mark it as resolved, or by reset+checkout (or whatever the voodooo is)
to discard the changes altogether. I don't remember needing to manually
"commit" myself. Normally I think I do:

M-x gitmerge
fix conflict
git add <file> to mark conflict resolved
  (unless eg smerge has automatically done that)
M-x gitmerge

So maybe it should just say "You don't have to commit the merge yourself..."



  parent reply	other threads:[~2018-06-11 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10 23:54 Resuming M-x gitmerge Noam Postavsky
2018-06-11  2:37 ` Eli Zaretskii
2018-06-11  6:54   ` João Távora
2018-06-11 12:40     ` Noam Postavsky
2018-06-11 15:30       ` Eli Zaretskii
2018-06-11 15:46         ` Stefan Monnier
2018-06-11 16:00           ` Eli Zaretskii
2018-06-11 16:14             ` Noam Postavsky
2018-06-11 15:50 ` Glenn Morris [this message]
2018-06-11 16:12   ` Noam Postavsky
2018-06-11 18:18     ` Glenn Morris
2018-06-11 19:31     ` David Engster
2018-06-12  0:48       ` Noam Postavsky
2018-06-19  0:27         ` Noam Postavsky

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=qm36xtjpar.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@gmail.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 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.