All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: git rev-list --author/--committer b0rked with -F/--fixed-strings
Date: Thu, 04 Sep 2008 08:47:37 +0200	[thread overview]
Message-ID: <g9o0ac$qig$1@ger.gmane.org> (raw)

Hello all,

I was recently looking into the reason why the gitweb search box
failed to provide results when using the author and committer
search and NOT using regexp searches.

I managed to track the fault down to the inability for git
rev-list to handle --author and --committer in conjunction with
the --fixed-strings option.

It's not difficult to see that the reason for this is that the
author and committer search patterns are *always* built as regular
expressions. However, I couldn't see any obvious way to do things
in a *different* way ...

So, is this a known bug (I would call it a bug, yes) in rev-list?
Are there any ideas around on how to fix it?

-- 
Giuseppe "Oblomov" Bilotta

             reply	other threads:[~2008-09-04  6:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04  6:47 Giuseppe Bilotta [this message]
2008-09-04  7:12 ` git rev-list --author/--committer b0rked with -F/--fixed-strings Junio C Hamano
2008-09-04  8:31   ` [PATCH] Teach "log -F --author=<match>" to behave better Junio C Hamano
2008-09-04 13:33     ` Teemu Likonen
2008-09-04 19:06       ` Junio C Hamano
2008-09-04 19:25         ` Teemu Likonen
2008-09-05  1:04           ` Junio C Hamano
2008-09-04 13:56     ` Giuseppe Bilotta
2008-09-04 14:09     ` Petr Baudis
2008-09-04 19:34       ` Junio C Hamano
2008-09-05 12:35         ` --all-match Teemu Likonen
2008-09-05  4:47       ` [PATCH] Teach "log -F --author=<match>" to behave better Junio C Hamano
2008-09-04 13:46   ` git rev-list --author/--committer b0rked with -F/--fixed-strings Giuseppe Bilotta

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='g9o0ac$qig$1@ger.gmane.org' \
    --to=giuseppe.bilotta@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.