>What does "which merge" tell you? If it turns up blank, you know the >problem. The merge program is usually found in the rcs package.
blank indeed. I guess I don't have rcs on this laptop.
thanks, -Len
>What does "which merge" tell you? If it turns up blank, you know the >problem. The merge program is usually found in the rcs package.
blank indeed. I guess I don't have rcs on this laptop.
thanks, -Len
Re: Is 'merge' in your path?
"Brown, Len" <len.brown@intel.com> wrote:
>>What does "which merge" tell you? If it turns up blank, you know the >>problem. The merge program is usually found in the rcs package. > > blank indeed. I guess I don't have rcs on this laptop.
Actually, I think git could use diff3 directly and not rely on "merge" from rcs which seems to be equivalent to "diff3 -m -E" (it might even call diff3, I'm not sure).
Are there any features in "merge" and not available in "diff3"?
-- Catalin
Re: Is 'merge' in your path?
Catalin Marinas <catalin.marinas@arm.com> writes:
> Are there any features in "merge" and not available in "diff3"?
`merge' from GNU RCS is just a wrapper around diff3.
--
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
| ever free! --Bryan W. Procter