On Thu, Nov 18, 2010 at 12:36 PM, Torgny Nyblom <[email protected]> wrote: > On Thursday 18 November 2010 11.59.28 Oswald Buddenhagen wrote: >> On Thu, Nov 18, 2010 at 11:16:04AM +0100, Torgny Nyblom wrote: >> > but "git log" has trouble following history due to a bug that makes it >> > loose parent commits somehow. >> >> git log has history simplification enabled by default. are you sure you >> aren't seeing the effect of that? > > Sure and sure > > I use "git log -C -C --follow" and that should follow history across renames > and copies even if the copy source was not touched in the current commit.
Whenever you provide a path to "git log" git simplifies the history, i.e. those commits not touching the path or those merge parents with "repeated" changes. It has nothing to do with --follow or -C. Can you try with --full-history? > Also I've seen others have the same issue on unrellated projects but so far > noone has had the time to produce a minimal example of the breakage. Even if you don't have a minimal example, but you "only" have an example using a public repository you can report it to the git mailing list. BTW, which is the problematic file and the hidden commit? Regards, Santi _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
