From: Glenn Morris <rgm@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Resuming M-x gitmerge
Date: Mon, 11 Jun 2018 14:18:12 -0400 [thread overview]
Message-ID: <y7vaap426z.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAM-tV-8Uq4p-0y_iuQjykd9cQ-09J_rHYBoAC-m3H0saLpEmeQ@mail.gmail.com> (Noam Postavsky's message of "Mon, 11 Jun 2018 12:12:09 -0400")
Noam Postavsky wrote:
> Hmm, this didn't work for me, I needed to commit the merge.
> And given the current implementation of gitmerge-repo-clean I can't
> see how it could work any other way.
I did:
git reset --hard f4e9ceacda
emacs -Q -l admin/gitmerge.el
M-x gitmerge
...
M-x kill-emacs
git add src/ftfont.c
git status now reports:
# All conflicts fixed but you are still merging.
# (use "git commit" to conclude merge)
#
# Changes to be committed:
#
# modified: ChangeLog.3
# modified: etc/NEWS
# modified: lisp/comint.el
# modified: lisp/simple.el
# modified: src/ftfont.c
At this point I can now run:
emacs -Q -nw -l admin/gitmerge.el
M-x gitmerge
and it prompts "resume merge?" and is happy to continue on "y".
This is how I've been doing it.
PS maybe totally unrelated, but I made this note a while ago, and never
investigated:
"is gitmerge discarding commits when there are more than one and then a
conflict? example: 20180302
emacs-26 0213c8b
master 82f12b2"
I'm no longer even sure what I meant, so feel free to ignore.
next prev parent reply other threads:[~2018-06-11 18:18 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
2018-06-11 16:12 ` Noam Postavsky
2018-06-11 18:18 ` Glenn Morris [this message]
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=y7vaap426z.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.