From: Jonas Fonseca Date: Sun, 29 May 2005 18:07:42 GMT Subject: Re: Problem with cg-merge Message-ID: <20050529180742.GA31388@diku.dk> In-Reply-To: <1117379092.7072.90.camel@pegasus> Marcel Holtmann wrote Sun, May 29, 2005: > Hi Petr, > > I saw that earlier, but I don't have any idea what's wrong here. If I do > a simple cg-update, I see something like this: > > Tree change: cf1f29d97210d0594dcf5b2a734bdb714de6bf24:89a14a5bd2c880095d5c618a102319bb3dc03da9 > :100755 100755 ceda2c50fc2c2941daa34a57722df251bf892c38 fea239b99d351502d1acb098abd725557f0af202 M cg-diff > :100755 100755 cc0c17beef75db41da3ad4ef8983bd7e222ac739 5f0bff77eb2110d52892793e5bef104acde7be32 M cg-help > > Applying changes... > Fast-forwarding cf1f29d97210d0594dcf5b2a734bdb714de6bf24 -> 89a14a5bd2c880095d5c618a102319bb3dc03da9 > on top of cf1f29d97210d0594dcf5b2a734bdb714de6bf24... > patching file cg-diff > patching file cg-help > cg-diff: needs update > cg-help: needs update > > This is a little bit odd, because if I call "git-diff-cache HEAD" after > it, I will see that cg-diff and cg-help are modified. After calling > cg-cancel everything looks fine again. The following change fixes cg-update for me. This is in tree_timewarp(). --- 0ca4ae56fa7bbd8d10e2c2791e389bc19977e460/cg-Xlib (mode:100755) +++ uncommitted/cg-Xlib (mode:100755) @@ -66,7 +66,7 @@ # XXX: This may be suboptimal, but it is also non-trivial to keep # the adds/removes properly. So this is just a quick hack to get it # working without much fuss. - cg-diff -r $branch >$patchfile + cg-diff >$patchfile fi git-read-tree -m "$branch" || die "$branch: bad commit" -- Jonas Fonseca