git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] jc/merge-theirs, rebased on top of mv/merge-in-c
Date: Mon, 23 Jun 2008 14:45:26 +0200	[thread overview]
Message-ID: <cover.1214224424.git.vmiklos@frugalware.org> (raw)

On Mon, Jun 23, 2008 at 12:15:35AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> Currently tip of 'pu' is broken and does not pass tests, as j6t/mingw
> has interaction with dr/ceiling and jc/merge-theirs has interaction
> with mv/merge-in-c.

Here is jc/merge-theirs, on top of mv/merge-in-c. Now all tests pass
here if I merge both to master.

To avoid unnecessary traffic, I do not send e0aafb4 ([PATCH 1/2]
git-merge-file --ours, --theirs"), as that is unchanged.

Junio C Hamano (2):
  git-merge-file --ours, --theirs
  git-merge-recursive-{ours,theirs}

 Documentation/git-merge-file.txt |   12 +++++++-
 Makefile                         |    3 ++
 builtin-merge-file.c             |   10 +++++-
 builtin-merge-recursive.c        |   37 ++++++++++++++++++++++---
 builtin-merge.c                  |    2 +
 git.c                            |    2 +
 ll-merge.c                       |   24 ++++++++++------
 ll-merge.h                       |    4 ++-
 t/t6034-merge-ours-theirs.sh     |   56 ++++++++++++++++++++++++++++++++++++++
 xdiff/xdiff.h                    |    8 +++++-
 xdiff/xmerge.c                   |   24 +++++++++++-----
 11 files changed, 155 insertions(+), 27 deletions(-)
 create mode 100755 t/t6034-merge-ours-theirs.sh

             reply	other threads:[~2008-06-23 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:45 Miklos Vajna [this message]
2008-06-23 12:45 ` [PATCH 2/2] git-merge-recursive-{ours,theirs} Miklos Vajna

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=cover.1214224424.git.vmiklos@frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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 NNTP newsgroup(s).