From: Jose Ricardo <josericardo.jr@gmail.com>
To: git@vger.kernel.org
Subject: Re: Custom Merge
Date: Mon, 23 Apr 2012 14:28:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20120423T162755-821@post.gmane.org> (raw)
In-Reply-To: 4F955243.2090103@viscovery.net
Johannes Sixt <j.sixt <at> viscovery.net> writes:
>
> I have my image merge script configured it like this:
>
> [merge "imgfile"]
> driver = imgmerge %O %A %B %A
>
> but if you do that, you must be sure that the script does not need to
> access $2 after it has begun writing to $4.
>
> (I know that it worked because at one time I had forgotten that I have a
> custom merge driver, and was expecting a merge conflict due to an image
> file, but there was no conflict, and the result was correct
>
Hi Johannes,
Thanks a lot for your help.
I have checked it and I'm writing to the right file after reading the data from
it. According to what I see, only the modifications made on the current
branch are saved, even after applying the delta to the right image file.
One question is: does it matter if I save the whole file, replacing the old with
this new one? Or do I need to open the old one and modify its content?
Thanks again!
prev parent reply other threads:[~2012-04-23 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:25 Custom Merge Jose Ricardo
2012-04-23 12:59 ` Johannes Sixt
2012-04-23 14:28 ` Jose Ricardo [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=loom.20120423T162755-821@post.gmane.org \
--to=josericardo.jr@gmail.com \
--cc=git@vger.kernel.org \
/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).