From: Junio C Hamano <junkio@cox.net>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: git log -S problem
Date: Sun, 20 May 2007 14:05:41 -0700 [thread overview]
Message-ID: <7vy7jjjjdm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200705202115.39325.johannes.sixt@telecom.at> (Johannes Sixt's message of "Sun, 20 May 2007 21:15:39 +0200")
Johannes Sixt <johannes.sixt@telecom.at> writes:
> There is something odd with -S of git log. Try this in your git.git:
>
> $ git log --pretty=oneline -Sbuiltin-merge-base -- Makefile
> 71dfbf224ff980f4085f75868dc409118418731e Make merge-base a built-in.
>
> $ git log --pretty=oneline -Smerge-base -- Makefile
> e468305a954d95a26bfcdec3bc6e4bd477d95676 [PATCH] Remove the explicit ...
> a3df180138b85a603656582bde6df757095618cf Rename git core commands ...
> cef661fc799a3a13ffdea4a3f69f1acd295de53d Add support for alternate ...
> e590d694ead8d50c2afc7086161d4ddc5d907655 Add more header dependencies.
> 6683463ed6b2da9eed309c305806f9393d1ae728 Do a very simple "merge-base"...
>
> $ git version
> git version 1.5.2
>
> I had expected that the set of commits found by the second search string are a
> proper superset of those found by the first one. What's wrong here? Why does
> a search for 'merge-base' not find occurences of 'builtin-merge-base'?
71dfbf224 removes one line that has "git-merge-base$X" and adds
one line that has "builtin-merge-base.o". If you count the
number of occurences of substring "builtin-merge-base" in the
preimage and the postimage, you see one addition. If you count
the same for substring "merge-base", the net difference is 0.
next prev parent reply other threads:[~2007-05-20 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 19:15 git log -S problem Johannes Sixt
2007-05-20 21:05 ` Junio C Hamano [this message]
2007-05-21 5:27 ` Johannes Sixt
2007-05-21 7:34 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy7jjjjdm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).