all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: In git, how does one revert a single file with merge conflicts in it?
Date: Mon, 2 Feb 2015 19:37:47 +0000	[thread overview]
Message-ID: <20150202193747.GE3673@acm.acm> (raw)
In-Reply-To: <jwvtwz4fc48.fsf-monnier+emacs@gnu.org>

Hello, Stefan.

On Mon, Feb 02, 2015 at 12:40:04PM -0500, Stefan Monnier wrote:
> >    $ git cherry-pick -xe <Commit Id>
> > , I get a half error message: "error: could not apply f3f7acc... ...".
> > Further investigation reveals that the cause is conflicts in a ChangeLog
> > file.  No surprises there.

> IIUC git did perform the merge, you simply have a file with a conflict
> as a result.  If you visit the file in Emacs, it should show you the
> conflicts and if once you've edited the file so as too remove the
> conflict markers, upon saving the result, Emacs should mark the file as
> "resolved" (which you can do manually with "git add lisp/ChangeLog").

OK.  I think what confused me was me thinking that there shouldn't be
"another" ChangeLog entry for the backported patch, given that there's
already one for the original patch.  But the ChangeLogs in Emacs 24 are
not the same files as those in Emacs 25.  Hence there needs to be an
entry in both of them.

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



      reply	other threads:[~2015-02-02 19:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 12:00 In git, how does one revert a single file with merge conflicts in it? Alan Mackenzie
2015-02-02 13:22 ` Andreas Schwab
2015-02-02 19:29   ` Alan Mackenzie
2015-02-03  9:04     ` Andreas Schwab
2015-02-03  9:26       ` David Kastrup
2015-02-03 22:36     ` Steinar Bang
2015-02-02 16:05 ` Eli Zaretskii
2015-02-02 19:32   ` Alan Mackenzie
2015-02-02 17:40 ` Stefan Monnier
2015-02-02 19:37   ` Alan Mackenzie [this message]

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=20150202193747.GE3673@acm.acm \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.