Comment 2 for bug 125773

On (16/07/07 20:34), John A Meinel wrote:
> I think there are a few possibilities for something like this.
>
> I would probably call it '--nick', just like you can search based on '--
> message'. 'bzr log --message REGEX' uses a regular expression, rather
> than a direct match, but I think we could do either for --nick. I
> wouldn't use a glob, though.
>
> One further possibility, would be to expose something like an SQL layer
> for queries. A possible implementation is to load all revision
> information, shove it into a sqlite :memory: file, and then run whatever
> SQL query the user asked. It would probably be a nice plugin to have
> around.
>
> It certainly would also be possible to keep the sqlite file around in a
> cache. Probably more of a plugin than a core feature. But '--nick' could
> certainly be a core feature. (Since generating branch-nick is a core
> feature)
>

That would give the ultimate flexibility.

An intermediate solution may be to expose a free text search, so that
you can have

  Branch nick: fix-12345

as the query to cover this use case, but it also works for people to
match other things like date, committer etc.

However then you may want to do

  Author: James Westby.*Fix 12345

to match across multiple fields, but then there needs to be an ordering
to the fields defined and maintained. This could be based on bzr log
output, but if new fields are added they would probably go before the
message there, but that may break complicated regexps.

Thanks,

James

--
  James Westby -- GPG Key ID: B577FE13 -- http://jameswestby.net/
  seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256