git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tim Visher" <tim.visher@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: 'Theirs' merge between branches on a binary file.
Date: Tue, 23 Dec 2008 09:05:17 -0500	[thread overview]
Message-ID: <c115fd3c0812230605x369af9c0n372db761fa11ce39@mail.gmail.com> (raw)
In-Reply-To: <7v3agfhk8b.fsf@gitster.siamese.dyndns.org>

On Mon, Dec 22, 2008 at 6:18 PM, Junio C Hamano <gitster@pobox.com> wrote:

> Hmph, I meant to point you at:
>
>    http://www.kernel.org/pub/software/scm/git/docs/git-checkout.html

Ah, yes.  There it is. :)

> I think you can use "git checkout-index --stage=3 path" if your git is
> older than that one with the option.
>
> v1.6.0.1-15-g38901a4 (checkout --ours/--theirs: allow checking out one
> side of a conflicting merge, 2008-08-30) introduced the feature.

Apparently this was added, at least to the docs, only in the latest
release?  That's kind of weird A) because the tag indicates 1.6.0.1,
not 0.6, and B) It's a pretty trivial operation in other VCSes.
Hmm... Maybe I'll try to updated the docs to make this feature a
little more visible.

Anyway, the checkout-index command does indeed work in the older
version.  That's kind of what I was looking for.  I'm now working on
compiling git under cygwin as the latest version cygwin installs for
you is 0.4!

Thanks for your help!

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 20:56 'Theirs' merge between branches on a binary file Tim Visher
2008-12-22 21:11 ` Junio C Hamano
2008-12-22 21:16   ` Tim Visher
2008-12-22 22:52     ` Junio C Hamano
2008-12-22 22:58       ` Tim Visher
2008-12-22 23:18         ` Junio C Hamano
2008-12-23 14:05           ` Tim Visher [this message]
2008-12-23 18:31             ` René Scharfe
2008-12-28 17:14               ` Tim Visher

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=c115fd3c0812230605x369af9c0n372db761fa11ce39@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --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).