Bruno Haible <bruno@xxxxxxxxx> wrote: > Is there some other concept or command that git offers? I'm in the situation > where I know that 'tr' in coreutils version 5.2.1 had a certain bug and > version 6.4 does not have the bug, and I want to review all commits that > are relevant to this. I know that the only changes in tr.c are relevant > for this, and I'm interested in a display of the minimum amount of relevant > commit messages. If "git log" is not the right command for this question, > which command is it? Two options come to mind: `git log v5.2.1..v6.4 -- tr.c` `git bisect` The former has a few different flavors, e.g. you can run the same arguments to `gitk` to view the changes in a graphical form. The latter will help you do a binary search through the commits which affected tr.c between the known good and known bad revisions, allowing you to test the possible candidates for the defect. > > > 2) Why so much system CPU time, but only on MacOS X? > > > > Probably the mmap() problem. Does it go away when you use git 1.5.0-rc4? > > No, it became even worse: git-1.5.0-rc4 is twice as slow as git-1.4.4 for > this command: > git-1.4.4: 25 seconds real time, 24 seconds of CPU time (12 user, 12 system) > git-1.5.0: 50 seconds real time, 39 seconds of CPU time (20 user, 19 system) That's not so good... This is `git log -- tr.c >/dev/null` ? -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html