{"thread":{"id":"22732","subject":"[BUG] ? - git log :/text results are strange","startedAt":"2010-02-19T21:50:39Z","lastAt":"2010-02-19T23:45:59Z","messageCount":4,"participants":["Eugene Sajine","Thomas Rast"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"135113","messageId":"76c5b8581002191350h61d6d8c2jd0245c0963fcc85f@mail.gmail.com","threadId":"22732","inReplyTo":null,"subject":"[BUG] ? - git log :/text results are strange","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-02-19T21:50:39Z","receivedAt":"2010-02-19T21:50:39Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\n\nWhen I’m executing\n$ git log :/fix\n\nI expect to see commits with messages starting from word “fix” only\nin git.git I’m getting a list of commits where some of messages are\nstarting from this word and some are not\n\nas this:\n\n$ git log :/fix\n\ncommit a525d2a41825530c01fd5eac497df0fcd82dca0b\nAuthor: Junio C Hamano <gitster@pobox.com>\nDate:   Tue Dec 8 22:16:55 2009 -0800\n\n   fixup! rebase -i --autosquash\n\ncommit 66a357d9bac24cc9b8419c256b5e35c327d2997c\nAuthor: Nanako Shiraishi <nanako3@lavabit.com>\nDate:   Tue Dec 8 12:13:14 2009 +0900\n\n   rebase -i --autosquash: auto-squash commits\n\n   Teach a new option, --autosquash, to the interactive rebase.\n   When the commit log message begins with \"!fixup ...\", and there\n   is a commit whose title begins with the same ..., automatically\n   modify the todo list of rebase -i so that the commit marked for\n   squashing come right after the commit to be modified, and change\n   the action of the moved commit from pick to squash.\n\n   Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>\n   Signed-off-by: Junio C Hamano <gitster@pobox.com>\n\ncommit 0205e72f088322a70a77643a7cd2d8b23ee07e14\nAuthor: Michael Haggerty <mhagger@alum.mit.edu>\nDate:   Mon Dec 7 10:20:59 2009 +0100\n\n   Add a command \"fixup\" to rebase --interactive\n\n   The command is like \"squash\", except that it discards the commit message\n   of the corresponding commit.\n\n   Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>\n   Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>\n   Signed-off-by: Junio C Hamano <gitster@pobox.com>\n\ncommit 163f3925902446735b2f631dc44ab67882a93024\nAuthor: Michael Haggerty <mhagger@alum.mit.edu>\nDate:   Mon Dec 7 05:22:58 2009 +0100\n\n   t3404: Use test_commit to set up test repository\n\n   Also adjust \"expected\" text to reflect the file contents generated by\n   test_commit, which are slightly different than those generated by the\n   old code.\n\n   Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>\n   Signed-off-by: Junio C Hamano gitster@pobox.com\n\nAnd so on…\n\nThis is reproducible problem on Linux env git v 1.6.5.6 and in msysgit\n1.6.4.msysgit.0\n\nThanks,\nEugene\n"},{"id":"135120","messageId":"201002192334.52495.trast@student.ethz.ch","threadId":"22732","inReplyTo":"76c5b8581002191350h61d6d8c2jd0245c0963fcc85f@mail.gmail.com","subject":"Re: [BUG] ? - git log :/text results are strange","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-02-19T22:34:52Z","receivedAt":"2010-02-19T22:34:52Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"On Friday 19 February 2010 22:50:39 Eugene Sajine wrote:\n> When I’m executing\n> $ git log :/fix\n> \n> I expect to see commits with messages starting from word “fix” only\n\nYou're not putting the puzzle together in the right way.  The chain\ngoes roughly like this:\n\n* git-log wants to know what its arguments resolve to\n\n  * (the internal equivalent of) git-rev-parse works out that :/fix is\n    a525d2a, as it (apparently) is the youngest commit with a message\n    starting with 'fix' (see man git-rev-parse)\n\n* git-log feeds a525d2a to the revision walker\n\n  * the revision walker starts outputting commits backwards through\n    history, starting from a525d2a\n\nand unsurprisingly, the log you pasted is just 'git log a525d2a'.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"135132","messageId":"76c5b8581002191541x95c3378je6f0528c11aaba4f@mail.gmail.com","threadId":"22732","inReplyTo":"201002192334.52495.trast@student.ethz.ch","subject":"Re: [BUG] ? - git log :/text results are strange","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-02-19T23:41:32Z","receivedAt":"2010-02-19T23:41:32Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"oh. I see, thanks!\n\nI had to do\n\n$git log --pretty=oneline | grep fix\n\nto get what i wanted...\n\nOn Fri, Feb 19, 2010 at 5:34 PM, Thomas Rast <trast@student.ethz.ch> wrote:\n> On Friday 19 February 2010 22:50:39 Eugene Sajine wrote:\n>> When I’m executing\n>> $ git log :/fix\n>>\n>> I expect to see commits with messages starting from word “fix” only\n>\n> You're not putting the puzzle together in the right way.  The chain\n> goes roughly like this:\n>\n> * git-log wants to know what its arguments resolve to\n>\n>  * (the internal equivalent of) git-rev-parse works out that :/fix is\n>    a525d2a, as it (apparently) is the youngest commit with a message\n>    starting with 'fix' (see man git-rev-parse)\n>\n> * git-log feeds a525d2a to the revision walker\n>\n>  * the revision walker starts outputting commits backwards through\n>    history, starting from a525d2a\n>\n> and unsurprisingly, the log you pasted is just 'git log a525d2a'.\n>\n> --\n> Thomas Rast\n> trast@{inf,student}.ethz.ch\n>\n"},{"id":"135133","messageId":"201002200045.59908.trast@student.ethz.ch","threadId":"22732","inReplyTo":"76c5b8581002191541x95c3378je6f0528c11aaba4f@mail.gmail.com","subject":"Re: [BUG] ? - git log :/text results are strange","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2010-02-19T23:45:59Z","receivedAt":"2010-02-19T23:45:59Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"On Saturday 20 February 2010 00:41:32 Eugene Sajine wrote:\n> oh. I see, thanks!\n> \n> I had to do\n> \n> $git log --pretty=oneline | grep fix\n> \n> to get what i wanted...\n\nWell, you can also do\n\n  git log --grep=fix --pretty=oneline\n\nSorry for not mentioning that in my first reply...\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"}]}