[PATCH] Interpret :/<pattern> as a regular expression Earlier, Git interpreted the pattern as a strict prefix, which made the operator unsuited in many cases. Now, the pattern is interpreted as a regular expression, on the whole message, so that you can say git diff :/.*^Signed-off-by:.Zack.Brown to see the diff against the most recent reachable commit which was signed off by Zack, whose Kernel Cousin I miss very much. If you want to match just the oneline, but with a regular expression, say something like git diff ':/[^ ]*intelligent' Since it makes more sense to match the beginning of a message (otherwise, a pattern like ':/git-gui: Improve' would match the _merge_ commit, pulling in the commit you are likely to want), the implementation uses the regmatch parameter of regexec() to anchor the pattern there. Signed-off-by: Johannes Schindelin <johannes.schindelin@xxxxxx> --- Anyone who can teach me how to match / not-match a newline using a more elegant syntax, please do so, by all means. Documentation/git-rev-parse.txt | 6 +++--- sha1_name.c | 31 +++++++++++++++++++++++++------ 2 files changed, 28 insertions(+), 9 deletions(-) diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt index 6380676..56e1561 100644 --- a/Documentation/git-rev-parse.txt +++ b/Documentation/git-rev-parse.txt @@ -194,9 +194,9 @@ blobs contained in a commit. found. * A colon, followed by a slash, followed by a text: this names - a commit whose commit message starts with the specified text. - This name returns the youngest matching commit which is - reachable from any ref. If the commit message starts with a + a commit whose commit message starts with the specified regular + expression. This name returns the youngest matching commit which + is reachable from any ref. If the commit message starts with a '!', you have to repeat that; the special sequence ':/!', followed by something else than '!' is reserved for now. diff --git a/sha1_name.c b/sha1_name.c index d9188ed..988d599 100644 --- a/sha1_name.c +++ b/sha1_name.c @@ -599,8 +599,8 @@ static int handle_one_ref(const char *path, /* * This interprets names like ':/Initial revision of "git"' by searching - * through history and returning the first commit whose message starts - * with the given string. + * through history and returning the first commit whose message matches + * the given regular expression. * * For future extension, ':/!' is reserved. If you want to match a message * beginning with a '!', you have to repeat the exclamation mark. @@ -611,34 +611,53 @@ static int get_sha1_oneline(const char *prefix, unsigned char *sha1) { struct commit_list *list = NULL, *backup = NULL, *l; int retval = -1; + regex_t regexp; + regmatch_t regmatch[1]; + char *temp_commit_buffer = NULL; if (prefix[0] == '!') { if (prefix[1] != '!') die ("Invalid search pattern: %s", prefix); prefix++; } - if (!save_commit_buffer) - return error("Could not expand oneline-name."); for_each_ref(handle_one_ref, &list); for (l = list; l; l = l->next) commit_list_insert(l->item, &backup); + if (regcomp(®exp, prefix, 0)) + return error("invalid regexp: %s", prefix); while (list) { char *p; struct commit *commit; + enum object_type type; + unsigned long size; commit = pop_most_recent_commit(&list, ONELINE_SEEN); parse_object(commit->object.sha1); - if (!commit->buffer || !(p = strstr(commit->buffer, "\n\n"))) + if (temp_commit_buffer) + free(temp_commit_buffer); + if (commit->buffer) + p = commit->buffer; + else { + p = read_sha1_file(commit->object.sha1, &type, &size); + if (!p) + continue; + temp_commit_buffer = p; + } + if (!(p = strstr(p, "\n\n"))) continue; - if (!prefixcmp(p + 2, prefix)) { + if (!regexec(®exp, p + 2, 1, regmatch, 0) && + regmatch[0].rm_so == 0) { hashcpy(sha1, commit->object.sha1); retval = 0; break; } } + if (temp_commit_buffer) + free(temp_commit_buffer); free_commit_list(list); for (l = backup; l; l = l->next) clear_commit_marks(l->item, ONELINE_SEEN); + regfree(®exp); return retval; } -- 1.5.2.1.2827.gba84a8-dirty - 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